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

Upgrade terraform-provider-databricks to v1.62.1 #686

Closed
pulumi-bot opened this issue Dec 31, 2024 · 5 comments · Fixed by #691
Closed

Upgrade terraform-provider-databricks to v1.62.1 #686

pulumi-bot opened this issue Dec 31, 2024 · 5 comments · Fixed by #691
Assignees
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@pulumi-bot
Copy link
Contributor

Release details: https://github.com/databricks/terraform-provider-databricks/releases/tag/v1.62.1

Note

This issue was created automatically by the upgrade-provider tool and should be automatically closed by a subsequent upgrade pull request.

@pulumi-bot pulumi-bot added the kind/enhancement Improvements or new features label Dec 31, 2024
@pulumi-bot
Copy link
Contributor Author

@pulumi-bot
Copy link
Contributor Author

@pulumi-bot
Copy link
Contributor Author

@pulumi-bot
Copy link
Contributor Author

VenelinMartinov added a commit that referenced this issue Jan 3, 2025
This PR was generated via `$ upgrade-provider pulumi/pulumi-databricks
--kind=provider`.

---

- Updating Java Gen version from 0.20.0 to 0.21.0.
- Upgrading terraform-provider-databricks from 1.58.0  to 1.62.1.
	Fixes #686
	Fixes #681
	Fixes #673
	Fixes #667
	Fixes #648


This PR adds a manual patch to work around an issue with a parameter
named Input which causes a class name clash in C sharp.
This was added instead of a rename does not work due to
pulumi/pulumi-terraform-bridge#2803
The pu/pu issue for the problem is
pulumi/pulumi#17826
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Jan 3, 2025
@pulumi-bot
Copy link
Contributor Author

This issue has been addressed in PR #691 and shipped in release v1.57.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants