gitlab-ci-pipelines-exporter: Allow specifying existing Secrets
#21
Conversation
This file contains 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
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.
This adds the ability to specify the name of
Secrets for the GitLab API token and the webhook token instead of specifying the values directly. You can specify either, both, or none this way, and they expect the values to be under different keys, so theSecretcan be the same for both if desired.I also extended the Makefile to allow validating all YAML files under
tests/so I could add tests for both directly specifying the values and specifying existingSecrets. These tests pass, and the revised chart works in a live cluster as well.Closes #18