fix: make packages registry secret optional #3
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.
Description
Fixes logic for generating registry credential secrets for
packages
. SinceregistryCredentials
are required via schema, updates logic to depend on required dockerconfigjson properties.Tests
Negative Test Case
Using default values from chart along with the following packages-values:
Chart successfully renders no
private-registry
secrets for eitherpackages
.Positive Test Case
Using default values from chart along with the following packages-values:
Successfully generates the following secrets:
For Issue
Closes #1710