RBAC for abort button or disable it at org level for all user except acc admin
complete
R
Representative Llama
Enhancement to the existing RBAC model, specifically roles so as to restrict a user(s) ability to initiate rollback on a pipeline. This user may have execute permissions, but this request is to deny those users with rollback of specific pipeline.
Log In
Canny AI
Merged in a post:
Disable `Abort Pipeline`
S
Scientific Finch
We want to disable the Abort Pipeline button because sometimes customers misuse it. After this action is executed, our rollback steps cannot be performed. Therefore, we want to disable this button to prevent users from aborting the pipeline.
Rohan Gupta
complete
This post was marked as
in progress
Sudarshan Purohit
next fiscal quarter
Sudarshan Purohit
Thank you for your ask. We have a planned feature to mark the Pipeline Failed (Similar to the Mark as Failure option for a stage), which can be used to shut down the pipeline in a controlled manner. This should solve the issue.
I see there is also an ask to disable Abort - this can be done once the above functionality is live.
S
Sole Chimpanzee
We have this use-case as well. Very important that we disable the ability for users to abort certain stages which leave the application in an inconsistent state.
R
Representative Llama
The ask is to allow rollback(Mark as failure) button but disable the abort button, so there is no inconsistency in the state with respected to the tracking by harness.
The cause of concern is that, in past week, a team has deployed the app, but before it reached to WrapUp stage it was aborted. That caused the issue as it was rolled out in k8s and harness was not aware of it. In the next canary run, it removed the secret associated with the aborted version, but since at k8s it rolled out. so, when it was required to scale up, it failed in doing so because the secret and config map was removed which caused a live issue.