Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check for the existence of private container registry password better #2339

Merged
merged 3 commits into from Nov 30, 2020

Conversation

shreddedbacon
Copy link
Member

Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated
  • PR title is ready for changelog and subsystem label(s) applied

In certain conditions, if an environment has a private container registry configured with credentials in the API at the project level, if any environment level variables are added then the private container registry credential would get set to an empty value and fail.

This checks that the credential is not empty before setting it, and also informs the user if no credential can be found.

Closing issues

closes #2338

@cdchris12 cdchris12 added the 2-build-deploy Build & Deploy subsystem label Nov 20, 2020
@cdchris12 cdchris12 added this to the v1.12.0 milestone Nov 20, 2020
Copy link
Contributor

@cdchris12 cdchris12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good eye! Looks good to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2-build-deploy Build & Deploy subsystem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants