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

Delete output directory if an error occurred #39

Open
aniruddha2000 opened this issue Jan 25, 2024 · 0 comments
Open

Delete output directory if an error occurred #39

aniruddha2000 opened this issue Jan 25, 2024 · 0 comments
Assignees
@aniruddha2000
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling needs refinement User stories that need to be refined for further progress

Comments

@aniruddha2000
Copy link
Member

Goals
In case that an error occurs, the user should know what went wrong. For this, he expects a good error message. Other than that the output directory which might already contain some of the generated files, should be deleted.

Otherwise, the user might think that the cluster stack release is usable, even though it is not. Additionally, we have to overwrite the directory anyway in case of a stable or beta release. This should not be necessary if the previous run fails.

/kind proposal
@aniruddha2000 aniruddha2000 self-assigned this Jan 25, 2024
@janiskemper janiskemper added the Container Issues or pull requests relevant for Team 2: Container Infra and Tooling label Jan 25, 2024
@jschoone jschoone added the needs refinement User stories that need to be refined for further progress label May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aniruddha2000 aniruddha2000

Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling needs refinement User stories that need to be refined for further progress
Projects
Sovereign Cloud Stack
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jschoone @aniruddha2000 @janiskemper