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

Add ability to pass an explicit registry value to Helm charts #2188

Merged
merged 4 commits into from
Jul 31, 2019
Merged

Add ability to pass an explicit registry value to Helm charts #2188

merged 4 commits into from
Jul 31, 2019

Conversation

michaelbeaumont
Copy link
Contributor

I've run into a problem deploying a chart based on stable/postgresql where an explicit registry value is expected when the templates are rendered. I'm not sure how common this pattern is amongst other charts but given that Postgres uses it and it seems reasonable in general, it seemed ok to me to add it as an option to Skaffold.

@codecov-io
Copy link

codecov-io commented May 28, 2019

Codecov Report

Merging #2188 into master will increase coverage by 0.03%.
The diff coverage is 88.88%.

Impacted Files Coverage Δ
pkg/skaffold/schema/latest/config.go 100% <ø> (ø) ⬆️
pkg/skaffold/docker/reference.go 100% <100%> (ø) ⬆️
pkg/skaffold/deploy/helm.go 64.9% <83.33%> (+0.59%) ⬆️

Copy link
Contributor

@tejal29 tejal29 left a comment

Choose a reason for hiding this comment

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

In general this looks an ok change.
Few nits:

  1. Please add unit tests for expliciteRegistry config
  2. The way we do config changes is a little bit hairy.
    • We first merge the PR where we freeze config.
    • Then merge the PR with config change.
      Can you revert the config freeze change from this PR?

@michaelbeaumont
Copy link
Contributor Author

1. Please add unit tests for expliciteRegistry config

2. The way we do config changes is a little bit hairy.
   
   * We first merge the PR where we freeze config.
   * Then merge the PR with config change.
     Can you revert the config freeze change from this PR?

Done, should I open a PR for the config? I left out the make generate-schemas and docs changes until after it's merged.

@dgageot dgageot added the kokoro:run runs the kokoro jobs on a PR label Jul 2, 2019
@kokoro-team kokoro-team removed the kokoro:run runs the kokoro jobs on a PR label Jul 2, 2019
@michaelbeaumont
Copy link
Contributor Author

@dgageot Can we run kokora again? could the time out have something to do with cloudflare's issues yesterday?

@dgageot dgageot added kokoro:run runs the kokoro jobs on a PR and removed kokoro:run runs the kokoro jobs on a PR labels Jul 3, 2019
@dgageot
Copy link
Contributor

dgageot commented Jul 4, 2019

@michaelbeaumont kokoro can't simply be retriggered. The easiest way would be for you to rebase on top of master.

@kokoro-team kokoro-team removed the kokoro:run runs the kokoro jobs on a PR label Jul 4, 2019
@michaelbeaumont
Copy link
Contributor Author

Pinging @tejal29 and @dgageot

pkg/skaffold/deploy/helm_test.go Outdated Show resolved Hide resolved
balopat
balopat previously requested changes Jul 9, 2019
pkg/skaffold/schema/latest/config.go Outdated Show resolved Hide resolved
@michaelbeaumont
Copy link
Contributor Author

Pinging @balopat

@michaelbeaumont
Copy link
Contributor Author

Pinging @tejal29 and @dgageot

@nkubala
Copy link
Contributor

nkubala commented Jul 29, 2019

sorry @michaelbeaumont, looks like you need one more rebase. once you do that CI should be green and I think this is good to go

@michaelbeaumont
Copy link
Contributor Author

@nkubala Done!

@michaelbeaumont
Copy link
Contributor Author

@nkubala Can we please get this merged 🙏

@nkubala nkubala dismissed balopat’s stale review July 31, 2019 20:41

comment addressed

@nkubala nkubala merged commit d7f1b59 into GoogleContainerTools:master Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants