Repository navigation
docs: say that a snapshotter can tag environments - #457
Conversation
The server now lets a snapshotter API key set and remove tags on an environment (kosli-dev/server#7416), so the role pages said less than the role can do. The permissions matrix splits tagging into a row for environments, open to snapshotters, and one for flows, repos and controls, which stays with members and above. The Snapshotter section, the overview table, the API footnote and the two one-line role summaries say the same. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Merge orderMerge after kosli-dev/server#7418 is deployed, or the docs describe a permission a snapshotter key does not yet have. Pages touched
|
|
Claude finished @sami-alajrami's task in 36s —— View job Doc review
No findings cleared the bar. The snapshotter tagging change is applied consistently in all three changed files, and no other page on the site contradicts it. The full review is in this comment. |
Doc reviewNo findings cleared the bar. The tagging change is applied consistently across all three role pages: the summary table, the permissions matrix, the † footnote and the Snapshotter accordion on 0 Critical, 0 Improvement, 0 Suggestion. This review is advisory only and does not block the merge. |
Say on the role pages that a snapshotter can set and remove tags on an environment, which
the server allows from kosli-dev/server#7418. The permissions matrix now has a row for
tagging environments, open to snapshotters, and one for flows, repos and controls, which
stays with members and above.
Part of kosli-dev/server#7416
🤖 Generated with Claude Code