Menu

1.2 Pipelines, too, had to drop the shared account
πŸ“°

1.2 Pipelines, too, had to drop the shared account

DEV Community: azureΒ·newbmiaoΒ·about 13 hours ago
#bku04aKG
#devtoazure#devto#dev#team#project
Reading 0:00
15s threshold

Background

Not long after the resource groups were split, Dee from the platform team spotted another problem.

The service connection behind relay's release pipeline still ran on a deployment identity holding Contributor on the entire subscription. When people found out, the reaction was mild surprise β€” the humans had been split into teams, but deployments still traveled the old shared road.

All three teams used the same Azure DevOps project. It had been the only one since the early days; teams kept arriving, and the project was never split.

While tracing one pipeline, Dee casually opened a variable group's Key Vault link: relay's production vault sat there in the pick list. The secret values stayed hidden β€” but the link itself went through. Nobody had ever reported it. The risk was real all the same.

He went through the whole project. Repos: visible and editable. Pipelines: visible and editable. Variable groups and project settings: same.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.