docs: Lead the cleanup section with the action that prevents leftovers - #12
Merged
Conversation
The cleanup section explained the CloudFormation ownership problem before telling the reader what to do about it, and it listed Lambda log groups as something to chase even though they expire on their own. It now opens with the action: delete the channels before destroying the stacks. That is enough to leave nothing behind, because deleting a channel removes its encoder password. The verification command stays for the case where the stacks were destroyed with channels still configured.
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
1 participant
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.
Summary
Rewrites the cleanup section so it leads with the action instead of the CloudFormation internals.
The previous text opened with "Two items are not stack-managed and need a check afterwards", which explains the mechanism before telling the reader what to do, and it listed Lambda log groups as something to chase even though they expire on their own from the retention period.
Change
The section now opens with the action that prevents leftovers: delete the channels before destroying the stacks. That is sufficient, because #11 made channel deletion remove the encoder password from Parameter Store. The verification command stays for operators who destroyed the stacks with channels still configured, and the log group behavior is one closing line rather than a bullet.
Documentation only. No code or infrastructure change.