Make cron to remove obsolete keys from estuary
Open
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
`GET https://api.estuary.tech/user/api-keys`
then
```js
keys.filter(({ expiry }) => new Date(expiry) < Date.now).map(({ id }) => id)
```
`DELETE https://api.estuary.tech/user/api-keys/:id`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the worker's scheduled-task or cron entry point and how it makes outbound requests. Use GET https://api.estuary.tech/user/api-keys, identify expired key IDs, and DELETE each corresponding /user/api-keys/:id endpoint. Done means expired keys are removed on the schedule without affecting unexpired keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100