feat: remove JUNO_TOKEN usage for deployments#745
Merged
peterpeterparker merged 1 commit intomainfrom Feb 20, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Juno now supports ephemeral access keys for deployments. These are generated and granted for 10 minutes (default duration) using OpenID Connect - a JWT generated by GitHub Actions. The repository has to be configured within the related Satellites (which I did).
Long story short, this approach is safer and cleaner than saving an identity in your repo. Cherry on top, the deployments will start appearing in the Console.
Notes
I deleted the
JUNO_TOKENfrom the repository secrets and from the Satellites.Changes
JUNO_TOKENusageid-token: writein the action — otherwise GitHub does not generate a JWT