🌱 chore: configure janitor to cleanup aws resources #413
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Enable
aws-janitor
to clean resources using a mark and delete approach (first execution mark/next delete), including:Resources that include the tag
janitor-ignore
will be skipped.Which issue(s) this PR fixes:
Fixes #368
Special notes for your reviewer:
This PR is waiting on an initial release of https://github.com/rancher-sandbox/aws-janitor, which will be created after rancher/aws-janitor#4.
aws-janitor
runs afterazure-janitor
. It will run even if the previous job fails and it'll be skipped only if the action is cancelled.Checklist: