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

Update helm charts with AzurePublicIPAddress.ipTags and new kustomize #1250

Merged
merged 1 commit into from
Aug 6, 2020

Conversation

babbageclunk
Copy link
Member

What this PR does / why we need it:
This regenerates the helm charts with the new field added in #1246.

The new version of kustomize no longer word-wraps long text fields like descriptions, which causes a lot of churn in the files. This was changed in kubernetes-sigs/kustomize#2678 released with kustomize 3.7.0 (after discussion on this bug kubernetes-sigs/kustomize#947).

Special notes for your reviewer:
This was split from #1249 so that the specific port changes weren't lost in the description changes.

How does this PR make you feel:
Relieved.

If applicable:

  • this PR contains documentation
  • this PR contains tests

The new version of kustomize no longer word-wraps long text fields
like descriptions, which causes a lot of churn in the files. This was
changed in kubernetes-sigs/kustomize#2678
released with kustomize 3.7.0 (after discussion on this bug
kubernetes-sigs/kustomize#947).
@@ -46,9 +41,11 @@ spec:
properties:
idleTimeoutInMinutes:
type: integer
ipTags:
Copy link
Member Author

Choose a reason for hiding this comment

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

The actual change from #1246.

@@ -32,8 +31,7 @@ spec:
singular: azuresqldatabase
preserveUnknownFields: false
scope: Namespaced
subresources:
status: {}
subresources: {}
version: v1alpha1
Copy link
Member

Choose a reason for hiding this comment

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

Removed status ?

Copy link
Member Author

Choose a reason for hiding this comment

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

It seems like this is an omitempty that's been added somewhere in the toolchain. (It's in the original PR too.)

@babbageclunk babbageclunk merged commit 348c438 into Azure:master Aug 6, 2020
@babbageclunk babbageclunk deleted the regen-helm branch August 6, 2020 02:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants