Allow tasks to access production via temporary maintainer tokens #1260
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.
Checklist
With the RBAC changes, access to the API via cli containers was given via guest permissions. This prevented the tasks from doing syncs from production environments. This PR adds a default maintainer user to every project, with no password and no ssh key (so logins with this user aren't allowed). Additionally, the api client requests a new access token for the maintainer and passes that to the task container. The ssh server was modified to allow passing a
LAGOON_TOKEN
environment variable that it will uses to check permissions.Changelog Entry
Improvement - Allow tasks to access production via temporary maintainer tokens (#1229)
Bugfix - Prevent lagoon images from interfering with pygmy
Closing issues
closes #1229