Group Deploy tokens to grant access to "shared projects" within a group
Problem to solve
You can share projects with other groups. This makes it possible to add a group of users to a project with a single action. And a deploy token created at the group level can be used across all projects that belong either to the specific group or to one of its subgroups.
However, a group deploy token does not grant access to any "Shared Projects" within the group.
User quote
As a Developer, I've got a group with most of the projects/images I need, but I also have some "shared" projects/images that I need the deploy token to have access to as well.
If the Group Deploy Token worked also with that shared projects/images it would fix all.
Intended users
User experience goal
A Developer can use their Deploy token for all projects within their group, including Shared projects.
Proposal
A Group deploy token may be granted Developer (or below) permissions on any shared projects within their group, so that they can push images and code to projects their group has been invited to.
Further details
Permissions and Security
- Similar to how shared projects work now, Developer will be a maximum level of permissions for shared projects.
- And it is possible to prevent projects in a group from sharing a project with another group. This allows for tighter control over project access.
Documentation
Availability & Testing
What does success look like, and how can we measure that?
Success looks like we help Developers work efficiently and safely by ensuring that Deploy tokens for all of their projects that they are responsible for.
Metrics
- Measure the number of Deploy tokens created (group vs. project)
- Measure the number of Deploy tokens used (group vs. project)
- Measure the number
What is the type of buyer?
Is this a cross-stage feature?
Yes, this impacts the Package stage and the Release stage