ECI-1923 add section about stack destroy issues to troubleshooting docs - #39678
Merged
johannzhang8 merged 2 commits intoSep 3, 2026
Merged
Conversation
Contributor
Preview links (active after the
|
estherk15
approved these changes
Sep 2, 2026
estherk15
left a comment
estherk15
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for adding this information!
|
|
||
| ## OCI stack destroy issues | ||
|
|
||
| If the destroy job fails or is unable to be run, clone the [OCI integration repository][11] and enter the repository directory. Then, use the [OCI integration cleanup script][10] to remove the remaining resources. Set the required variables, then review a dry run: |
Collaborator
There was a problem hiding this comment.
Optional suggestion, I wonder if this is easier to read as a list.
Suggested change
| If the destroy job fails or is unable to be run, clone the [OCI integration repository][11] and enter the repository directory. Then, use the [OCI integration cleanup script][10] to remove the remaining resources. Set the required variables, then review a dry run: | |
| If the destroy job fails or is unable to run: | |
| 1. Clone the [OCI integration repository][11] and enter the repository directory. | |
| 2. Use the [OCI integration cleanup script][10] to remove the remaining resources. | |
| 3. Set the required variables. | |
| 4. Review a dry run: |
johannzhang8
deleted the
johannzhang8/eci-1923-document-stack-destroy-errors
branch
September 3, 2026 13:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Add a section about failed stacks, with no way of being able to destroy them
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes