You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to this "Feature: Required Mandatory Group for deployment approval", we would need to have a group approval mechanism for config protections(deployment templates) instead of generic super-user approvals.
🎤 Pitch / Usecases
Because it's hard to provide super-admin access for the peoples just to provide approval for config changes. So if we have a specific group wise people nomination for config protection would be able to have a fine-grained access control for the config / deployment template related changes.
🔄️ Alternative
Not sure we have any alternative / workaround for this at the moment ui.
👀 Have you spent some time to check if this issue has been raised before?
Hey @sathish-ather, this feature request is in our planning phase as of now, I can confirm you a tentative date once we have have finalised the implementation details. I'm hoping the criticality (P1) still remains same for you, feel free to ping me back if there's any change in the priority, we can connect over call to see how I can fast-track this for you.
🔖 Feature description
Hey Team,
Similar to this "Feature: Required Mandatory Group for deployment approval", we would need to have a group approval mechanism for config protections(deployment templates) instead of generic super-user approvals.
🎤 Pitch / Usecases
Because it's hard to provide super-admin access for the peoples just to provide approval for config changes. So if we have a specific group wise people nomination for config protection would be able to have a fine-grained access control for the config / deployment template related changes.
🔄️ Alternative
Not sure we have any alternative / workaround for this at the moment ui.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: