-
Notifications
You must be signed in to change notification settings - Fork 121
Upgrade Go SDK to v0.89.0 #3870
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
Conversation
| // Version could v0.0.0-dev+21e1aacf518a or just v0.0.0-dev (the latter is currently the case on Windows) | ||
| devVersionRegex = regexp.MustCompile(`0\.0\.0-dev(\+[a-f0-9]{10,16})?`) | ||
| // Matches databricks-sdk-go/0.90.0 | ||
| sdkVersionRegex = regexp.MustCompile(`databricks-sdk-go/[0-9]+\.[0-9]+\.[0-9]+`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: this means fewer diffs in the acceptance tests where recorded requests from Terraform show up with an older/newer SDK version until the TF dep is updated.
11 failing tests:
|
|
|
||
| cmd.Flags().Var(&createJson, "json", `either inline JSON string or @path/to/file.json with request body`) | ||
|
|
||
| cmd.Flags().BoolVar(&createReq.AllowDuplicateNames, "allow-duplicate-names", createReq.AllowDuplicateNames, `If false, deployment will fail if name conflicts with that of another pipeline.`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be quite a big of backward incompatible change, shall we call it out at least in release notes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for flagging! I missed it when eyeballing the diff.
I'll investigate to see what happened to the field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see it's not just the flag but all flags...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They were added by mistake in #3769.
It was corrected in a later SDK release and that's now picked up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These flags were never intended to be added. Both the jobs create and pipeline create commands should always take a --json because the payloads are too complex to be specified via flags.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I included this in the PR summary and added a changelog entry.
## Changes * https://github.com/databricks/terraform-provider-databricks/releases/tag/v1.96.0 * https://github.com/databricks/terraform-provider-databricks/releases/tag/v1.95.0 ## Why Nominal upgrade to match the SDK version in #3870.
## Release v0.276.0 ### CLI * Remove previously added flags from the `jobs create` and `pipelines create` commands. ([#3870](#3870)) ### Bundles * Updated the default-python template to follow the Lakeflow conventions: pipelines as source files, pyproject.toml ([#3712](#3712)). * Fix a permissions bug adding second IS\_OWNER and causing "The job must have exactly one owner." error. Introduced in 0.274.0. ([#3850](#3850))
Changes
See https://github.com/databricks/databricks-sdk-go/releases/tag/v0.89.0
This change removes previously added flags to the
jobs createandpipelines createcommands. These flags were not part of these commands before and were added by accident (in #3769). Because the payload for these commands is complex, they take a--jsonflag instead.