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
Today, if you create an application with sub-resources (e.g. container) and delete the application via API call, the sub-resource (container) will not be deleted. This can cause hanging resources.
Acceptance criteria
TBD. We should think about this scenario and come to a consensus on what the API behavior should be (should it delete the hanging resources, return an error, or do nothing)
👋 @willdavsmith Thanks for filing this feature request.
A project maintainer will review this feature request and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Overview of feature request
Today, if you create an application with sub-resources (e.g. container) and delete the application via API call, the sub-resource (container) will not be deleted. This can cause hanging resources.
Acceptance criteria
TBD. We should think about this scenario and come to a consensus on what the API behavior should be (should it delete the hanging resources, return an error, or do nothing)
Additional context
No response
Would you like to support us?
AB#13851
The text was updated successfully, but these errors were encountered: