-
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 from 2020-12-01 to 2021-08-01 #14312
Conversation
27bf6bd
to
2941ae0
Compare
@oWretch Just a small comment based on previous work done by others, we'd need to check backward compatibility with resources provisioned with the old API version. This was a problem previously, not sure about now. |
What I currently see with APIM in our environment is if you deploy a core component of a resource that requires a new API version you cannot edit the resource with an older API version. That matches my reading of the reported issue above (#12566 (comment)). We have manually updated an APIM instance to be deployed in zones. Because this is a feature that requires the 2021-01-01-preview API version, when we run terraform and attempt to change the I'll run more tests with the updated provider tomorrow and make sure our non-zonal APIM instances which are managed on the old API version are still manageable on the new. |
Hi there and thank you for adding this. One small remark from my side - this change not only brings APIM API upgrade, but a complete SDK upgrade, which is... somewhat more involved. Whereas it might seem that same versions of packages should stay the same between different SDK versions, in practice it's now always the case. |
Agreed @favoretti. We need the SDK upgrade to get the API version. And there was a recent commit to bring the SDK up to v59.2.0, so we are not making a large jump in this PR. |
I've reviewed our existing APIM instances that were created with the previous API Version, and they are all reading correctly with the updated API. While not a test of all provider functionality, it indicates that the versions are backwards compatible for existing services. |
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 @oWretch, left a comment inline on what to do with the sample property
2941ae0
to
c44b678
Compare
c713281
to
e62bf0a
Compare
2900b90
to
aa903fa
Compare
aa903fa
to
1f83388
Compare
1f83388
to
a73f458
Compare
Have a panic in the tests @oWretch
|
ApiOperation tests all now passing
|
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 @oWretch! LGTM 🚀
This functionality has been released in v2.90.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! |
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. |
Microsoft added a large amount of functionality in 2021-01-01-preview for API Management. This PR is to move us to the latest stable API release, which will allow for adding functionality to resolved issues such as #12021 and #13445. It updates all the constants which were renamed.
The only potential regression is that
Sample
is no longer a property in theOperationRepresentation
schema. It has been replaced with a map ofExamples
. I can update the schema, but I'm not sure how to deal with the value property of theParameterExampleContract
. If someone can help me with this, I'll push the code for the Examples.My plan is to uplift the features in separate PRs.