-
Notifications
You must be signed in to change notification settings - Fork 461
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
Replacing EnvironmentAjaxAction by EnvironmentResource #28578
Comments
When adding the "allowed" roles permissions, the api now takes only RoleIds which can be hard to deal with. What we need to allow on the end point is to be able to pass a List which can be made up of roleIds, roleKeys, userIds and/or user emails, in that order. We should try to resolve what is passed in as we iterate over the list of strings when building the permissions for the env |
That would be fantastic to allow the API to take userId/email, role names as well (and let the system resolve these internally). That would really make it easy for setting up endpoints. |
Noted, working on it |
Parent Issue
No response
User Story
As an user, I want to be able to create an PP env by using rest
Acceptance Criteria
UI uses the new endpoint to create a PP env
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
Postman test for create env
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: