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.

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

Feature: Retrigger Manifest on error #1617

Open
1 task
Despire opened this issue Dec 18, 2024 · 0 comments
Open
1 task

Feature: Retrigger Manifest on error #1617

Despire opened this issue Dec 18, 2024 · 0 comments
Labels
feature New feature

Comments

@Despire
Copy link
Contributor

Despire commented Dec 18, 2024

Description

Errors can occur during the execution of the manifest through the individual services. The aim of this feature would be to introduce a way for the user to trigger the rescheduling of the manifest. Why would this be needed ?

Currently the only way to trigger a reschedule is with changes to the InputManifest. While this works most of the time if there are any infrastructure issues, (i.e. the user can replace wrong nodepools with correct ones), there is no mechanism to retrigger the manifest if an error occurs after the infrastructure has been spawned correctly (i.e an error occurs during the ansibler, kube-eleven, kuber stage).

It would be beneficial to come up with a mechanism that would allow to retrigger the InputManifest in such cases.

Exit criteria

  • Possibility of triggering the workflow for a manifest manually by the user.
@Despire Despire added the feature New feature label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

1 participant