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

fix(kubernetes): explicitly set v1 k8s account providerVersion #15

Merged
merged 1 commit into from
Feb 26, 2020

Conversation

maggieneterval
Copy link
Contributor

In order to prepare for the upcoming removal of Spinnaker's Kubernetes V1 provider, we changed the default for accounts without a providerVersion from v1 to v2. To fix the integration tests, we need to explicitly specify v1 as the providerVersion for the v1 tests.

(Apologies for not anticipating that the providerVersion would be unspecified in these tests!)

dev/validate_bom__config.py Outdated Show resolved Hide resolved
@maggieneterval
Copy link
Contributor Author

Was wondering why this didn't seem to be taking effect on any run except master, but then realized that buildtool has release branches! Going to cherry-pick this into each release branch now.

@maggieneterval
Copy link
Contributor Author

@spinnakerbot cherry-pick 1.18

@maggieneterval
Copy link
Contributor Author

@spinnakerbot cherry-pick 1.17

@maggieneterval
Copy link
Contributor Author

@spinnakerbot cherry-pick 1.16

@spinnakerbot
Copy link
Collaborator

Cherry pick successful: #16

@spinnakerbot
Copy link
Collaborator

Cherry pick successful: #17

@spinnakerbot
Copy link
Collaborator

Cherry pick successful: #18

maggieneterval added a commit that referenced this pull request Feb 26, 2020
…18)

Co-authored-by: Maggie Neterval <mneterval@google.com>
maggieneterval added a commit that referenced this pull request Feb 26, 2020
…17)

Co-authored-by: Maggie Neterval <mneterval@google.com>
maggieneterval added a commit that referenced this pull request Feb 26, 2020
…16)

Co-authored-by: Maggie Neterval <mneterval@google.com>
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.

3 participants