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

fix: rbac: update of a step state is reserved to template owners only #307

Merged
merged 1 commit into from
Dec 29, 2021

Conversation

rbeuque74
Copy link
Member

  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
    Fix

  • What is the current behavior? (You can also link to an open issue here)
    Previously, edition of the step state was allowed to resolvers. But
    resolvers are regular users, that have the right to resolve the task,
    they are not aware of the behaviour of the template.

  • What is the new behavior (if this is a feature change)?
    This power should be reserved to template owners, who wrote the template, and know how the
    steps state can be changed.

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
    Yes: resolver users used to have the right to change the step state: this is now reserved to admins and allowed_resolver_usernames of the task_template.

cc @simonmartinez in case RBAC need to be adapted on the UI

  • Other information:

Previously, edition of the step state was allowed to resolvers. But
resolvers are regular users, that have the right to resolve the task,
they are not aware of the behaviour of the template. This power should
be reserved to template owners, who wrote the template, and know how the
steps state can be changed.

Signed-off-by: Romain Beuque <556072+rbeuque74@users.noreply.github.com>
@rbeuque74 rbeuque74 requested review from loopfz and wI2L December 24, 2021 11:48
@rbeuque74 rbeuque74 merged commit ad68312 into master Dec 29, 2021
@rbeuque74 rbeuque74 deleted the change-rbac-edit-step-state branch December 29, 2021 10:04
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

Successfully merging this pull request may close these issues.

2 participants