You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
assets for manual testing, when developers try things out
assets used for integration testing, which are used in CI
we should label all the cloud assets used for integration tests with ci:integration labels so they don't get deleted by accident and it is clear why they exists.
bonus points - add an owner: <name> label based on who created them.
Definition of done
figure out which assets are used for integration tests
add a ci:integration label to all of them
Out of scope
using CloudCustodian to automatically label assets (?)
The text was updated successfully, but these errors were encountered:
@oren-zohar, you're right about AWS resources, but we also need to consider GCP and Azure accounts, which haven't received as much attention regarding labeling.
Motivation
we usually deploy 2 types of assets:
we should label all the cloud assets used for integration tests with
ci:integration
labels so they don't get deleted by accident and it is clear why they exists.bonus points - add an
owner: <name>
label based on who created them.Definition of done
ci:integration
label to all of themOut of scope
The text was updated successfully, but these errors were encountered: