Expiry field on resources
Open
enhancement
- Dominant language
- Python
- Stars
- 407
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
In the world of automation, no looking back, moving fast and breaking things it greatly simplify extra work to have an expiry field on resources. This is a datetime field that renders a resource as either orphaned and easily reportable, hidden and ready to overwrite, or deleted - I mostly lean toward the former.
An example use case would be running a periodic job to push updates to NSoT about a resource, either from local server or EC2 or anything, that gets decommed suddenly and letting it be cleaned up nicely.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.