Please vote on this PR by adding a :thumbsup: reaction to the original PR to help the community and maintainers prioritize for review
Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review
Description
To deprecate 1.0 and 1.1 for minimum_tls_version per the announcement
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change.
[x] I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
[x] I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
[x] I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
For example: “resource_name_here - description of change e.g. adding property new_property_name_here”
Changes to existing Resource / Data Source
[x] I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
[ ] I have written new tests for my resource or datasource changes & updated any relevent documentation.
[x] I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
[ ] (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.
draft to run tests
Testing
[x] My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)
4.0 :
5.0:
As these failures shall not be caused by this PR, can we tolerate it?
Community Note
Description
To deprecate
1.0
and1.1
forminimum_tls_version
per the announcementPR Checklist
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
draft to run tests
Testing
4.0 :
5.0:
As these failures shall not be caused by this PR, can we tolerate it?
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_cosmosdb_account
- update for TLS 1.0&1.1 retirement [GH-27986]This is a (please select all that apply):
Related Issue(s)