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
We occasionally see CF resources not being deleted after the test has completed on Concourse. It is quite hard to investigate what happened and why the objects have not been finalized, so lets find a way to annotate them
Action to take
All CF resources support metadata (labels and annotations) when created via the CF API. Our e2e tests could supply a label on those object that says what is the test currently being executed (Ginkgo has some APIs to get the current test context).
It could turn out that some Korifi endpoints do not support metadata when creating objects. If that is the case, create stories to fix that - we need to support metadata anyway in order to be CF API compliant.
The text was updated successfully, but these errors were encountered:
Background
We occasionally see CF resources not being deleted after the test has completed on Concourse. It is quite hard to investigate what happened and why the objects have not been finalized, so lets find a way to annotate them
Action to take
All CF resources support metadata (labels and annotations) when created via the CF API. Our e2e tests could supply a label on those object that says what is the test currently being executed (Ginkgo has some APIs to get the current test context).
It could turn out that some Korifi endpoints do not support metadata when creating objects. If that is the case, create stories to fix that - we need to support metadata anyway in order to be CF API compliant.
The text was updated successfully, but these errors were encountered: