Skip to content

tuf: Create separate SAs for publish and sign#217

Merged
jku merged 1 commit into
sigstore:mainfrom
jku:tuf-sa-refactor
May 18, 2026
Merged

tuf: Create separate SAs for publish and sign#217
jku merged 1 commit into
sigstore:mainfrom
jku:tuf-sa-refactor

Conversation

@jku
Copy link
Copy Markdown
Member

@jku jku commented May 15, 2026

  • Separate SAs is cleaner and allows separate role bindings
  • Keep the (now deprecated) "tuf-gha" SA in place to make sure transition is smooth: it can be removed once it's not used in any environment
  • Remove unnecessary depends_on fields
  • Add outputs for the new SA emails for easier use outside the module

@jku jku requested a review from a team as a code owner May 15, 2026 13:03
* Separate SAs for different GCP roles is cleaner
  and allows separate role bindings
* Keep the (now deprecated) "tuf-gha" SA in place
  to make sure transition is smooth: it can be removed
  once it's not used in any environment
* Remove unnecessary depends_on fields
* Add outputs for the new SA emails for easier use outside
  the module

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
@jku jku force-pushed the tuf-sa-refactor branch from 99a3869 to 3afc345 Compare May 15, 2026 13:05
@jku jku merged commit 1db2854 into sigstore:main May 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants