Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Persist original deployment inputs somewhere in stack. #616

Open
sobolk opened this issue Nov 9, 2023 · 0 comments
Open

Persist original deployment inputs somewhere in stack. #616

sobolk opened this issue Nov 9, 2023 · 0 comments
Labels
debugging Issues that will improve debuggability of CLI and backend tools tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later

Comments

@sobolk
Copy link
Member

sobolk commented Nov 9, 2023

Follow up from #594 .

Now that we truncate and hash inputs for stack naming purposes we should also stash unmodified inputs somewhere in stack metadata, so that information is available for troubleshooting purposes.
@sobolk sobolk added tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later debugging Issues that will improve debuggability of CLI and backend tools and removed release-blocker labels Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
debugging Issues that will improve debuggability of CLI and backend tools tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sobolk @ashish-aws