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
A common feature for platforms like this is the ability to generate multiple API Keys. It would be very helpful if we have those set up. This ties in well with #838 which allows resetting the API Keys.
An additional advantage to this would be that it would make it easier to implement Role-Based Access Control (RBAC) down the lane. You could potentially generate a different project-scoped key for the CI/CD pipeline versus a different user-scoped key for developers.
Suggestion or Example of how the feature would be used
No response
Duplicate declaration
I have searched the issues and this feature has not been requested before.
The text was updated successfully, but these errors were encountered:
Yip, this does sound great. We will eventually have teams support, which will require roles and multiple keys. So I agree with Oddbjorn, we won't start with this yet (at least not from within Shuttle), but will eventually.
But if anyone in the community wants to look into it in the mean time, feel free to reach out with a plan of suggested updates 😄
Describe the feature
A common feature for platforms like this is the ability to generate multiple API Keys. It would be very helpful if we have those set up. This ties in well with #838 which allows resetting the API Keys.
An additional advantage to this would be that it would make it easier to implement Role-Based Access Control (RBAC) down the lane. You could potentially generate a different project-scoped key for the CI/CD pipeline versus a different user-scoped key for developers.
Suggestion or Example of how the feature would be used
No response
Duplicate declaration
The text was updated successfully, but these errors were encountered: