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

[RFE] Automate - Expose max_retries override at instance level #3560

Closed
ghost opened this issue Mar 9, 2018 · 2 comments
Closed

[RFE] Automate - Expose max_retries override at instance level #3560

ghost opened this issue Mar 9, 2018 · 2 comments
Assignees

Comments

@ghost
Copy link

ghost commented Mar 9, 2018

When one creates a state machine, the maximum number of retries for a state is set at the class level. However, a use case of state machines is to create generic state machines where the state name is 'StateX' and URI is specified only at the instance level, not the class. In this case, to stay generic, one is tempted to set the maximum number of retries to a very high number for each state, to cover whatever situation at the instance level.

Allowing to override the maximum number of retries at the instance level would help creating generic state machine classes (scaffolds) with no maximum retries set, and then let the instance specify the maximum retries based on the actual URI.

According to @mkanoor, the max_retries can already be set at the instance level in the backend code, but the UI currently doesn't support it. So I create this issue to politely ask for someone to add this in th Classic UI.

XRef: ManageIQ/manageiq-automation_engine/issues/163
Associated BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1596338

@gmcculloug
Copy link
Member

@miq-bot assign @h-kataria

@ghost
Copy link
Author

ghost commented Mar 20, 2018

Tried and tested. Works as expected.

@ghost ghost closed this as completed Aug 24, 2018
@ghost ghost reopened this Aug 24, 2018
@ghost ghost closed this as completed Aug 24, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants