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
{{ message }}
Repository navigation
Commit 76d418f
Browse filesBrowse the repository at this point in the historyBrowse files
Add --force flag to rad resource delete and rad app delete
Add a --force option to both 'rad resource delete' and 'rad app delete'
commands that allows users to delete resources stuck in non-terminal
provisioning states (e.g., Updating, Accepted).
Server-side: DefaultAsyncDelete reads a 'force' query parameter and
skips the provisioning state conflict check when force=true, while
still validating ETags and running delete filters.
Client-side: A forceDeletePolicy pipeline policy injects force=true
as a query parameter when the force option is set.
CLI: Both commands accept --force, display a warning about potential
orphaned external resources, and pass the flag through to the API.
// Run executes asynchronous delete operation by validating the request, executing custom delete filters, and starting async job, and returns an async response.
45
+
// When the "force" query parameter is set to "true", the provisioning state check is skipped,
46
+
// allowing deletion of resources stuck in non-terminal states (e.g., "Updating").
progressText:=fmt.Sprintf("Deleting application '%s' from environment '%s'...", r.ApplicationName, r.EnvironmentName)
193
203
204
+
ifr.Force {
205
+
r.Output.LogInfo("WARNING: Force deleting an application. Resources in non-terminal states may leave orphaned external resources that require manual cleanup.")
0 commit comments