Adding access token prompt for GitLab Secure Files Match #21279
Merged
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
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validci/circleci
builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)Motivation and Context
The authentication part of the GitLab Match storage backend can be confusing and the error messages are hard to understand. As reported in: #20525
Description
This change adds better error messaging as well as a prompt to supply the access token when it can't be found.
Testing Steps
fastlane match
withgitlab_secure_files
configured as the storage backend.PRIVATE_TOKEN=foo fastlane match
withgitlab_secure_files
configured as the storage backend.