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

Consider mechanism for error events #25

Closed
eytan-avisror opened this issue Aug 19, 2019 · 1 comment
Closed

Consider mechanism for error events #25

eytan-avisror opened this issue Aug 19, 2019 · 1 comment
Labels
enhancement New feature or request future Future enhancements

Comments

@eytan-avisror
Copy link
Collaborator

Right now when a stack is in error state, there is no way of knowing why it go to error state without looking at controller logs or looking at CF stack status.
We should collect this information and possibly place it under .status.message or even / and publish kubernetes events to describe what happened
@eytan-avisror eytan-avisror added the enhancement New feature or request label Aug 19, 2019
@eytan-avisror eytan-avisror added this to the 0.4.0 milestone Aug 19, 2019
@eytan-avisror eytan-avisror mentioned this issue Sep 14, 2019
Closed
@eytan-avisror eytan-avisror modified the milestones: 0.4.0, 0.5.0 Oct 30, 2019
@eytan-avisror eytan-avisror removed this from the 0.5.0 milestone May 9, 2020
@eytan-avisror eytan-avisror added the future Future enhancements label May 9, 2020
@eytan-avisror
Copy link
Collaborator Author

no longer relevant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request future Future enhancements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eytan-avisror