Skip to content

feat: pass --wait when deleting compute-envs during overwrite#267

Open
robsyme wants to merge 1 commit intomainfrom
fd7252-delete-wait
Open

feat: pass --wait when deleting compute-envs during overwrite#267
robsyme wants to merge 1 commit intomainfrom
fd7252-delete-wait

Conversation

@robsyme
Copy link
Copy Markdown
Member

@robsyme robsyme commented Mar 30, 2026

Summary

  • When on_exists: overwrite deletes a compute environment, appends --wait to the tw compute-envs delete command
  • This blocks until the CE is fully deleted before seqerakit proceeds to create the replacement
  • Other resource types (credentials, pipelines, etc.) are unaffected

Context

Forge CE deletion is async (~2 minutes). seqerakit's overwrite flow deletes the CE and immediately creates the replacement, which fails because the old CE is still in DELETING status. Adding --wait makes the delete call block until the CE is gone.

Depends on: seqeralabs/tower-cli#593 — the tower-cli change must ship first.

Related: FD-7252

Test plan

  • test_delete_resource_compute_envs_includes_wait: verifies --wait is appended for compute-envs
  • test_delete_resource_credentials_does_not_include_wait: verifies other resources are unaffected
  • Full test suite: 120/120 pass

🤖 Generated with Claude Code

When seqerakit deletes a compute environment as part of an overwrite
operation, it now appends --wait to the tw CLI args so the delete
blocks until the CE is fully removed before re-creating it.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Signed-off-by: Rob Syme <rob.syme@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant