-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 Api Management Version from 2020-12-01 to 2021-01-01-preview #12566
Conversation
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.
build in TC fails:
[16:39:50] [Step 4/5] api_management_api_release.go:8:2: cannot find package "." in:
[16:39:50] [Step 4/5] /opt/teamcity-agent/work/a73be106926a7472/vendor/github.com/Azure/azure-sdk-for-go/services/apimanagement/mgmt/2020-12-01/apimanagement
Hi kt, I've updated the PR with the latest upstream change. Except one |
Temporarily closed for the blocker of |
This functionality has been released in v2.70.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Hi! Do You plan to resume working on this issue? Currently if you create APIM via terraform and manually assign availability zones with internal vnet - it completely breaks terraform workspace - because terraform unable to read the APIM state.
|
@JeffreyRichter that seems like an API bug, where a resource is modified on one API Version but can't be retrieved on an older one? |
If you're saying that just modifying a resource with a new api-version value makes the resource completely ungettable with an old api-version value, then that is a breaking change and is not allowed by Azure's versioning policies. However, we occasionally DO allow an exception to this, but it requires that the service team fully document this behavior so that customers completely understand that updating a resource with a new api-version means that it will be inaccessible to a client using an old api-version so that customers are consciously and explicitly opting into this behavior on their schedule. I'm guess that this documentation was done here, or you would have been expecting this behavior rather than being surprised by it. If so, then this change is against Azure's policies. Plus, I would have been notified of this break and I don't recall hearing about this one and so it likely is a violation of Azure's versioning policies. I'll contact some people closer to this issue. Thanks for bringing this to my attention. |
Interesting enough I was able to set the public IP, and the AV Zone through a combination of Terraform and ARM but never lost terraform functionality after
Tf to implement
|
I'll tracking this problem with service team. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
To fix #12125 to support
PublicIPAddress
to allow setting zone in api management service in vnet