azurerm_postgresql_server
- deprecate ssl_enforcement_enabled
and ssl_minimal_tls_version_enforced
no longer accpets TLSEnforcementDisabled
, TLS1_0
or TLS1_1
as a value in 5.0
#28247
+138
−49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Description
As the announcement, update the documents and deprecate tls 1.0 and tls 1.1 in v5.0
Also, deprecate
ssl_enforcement_enabled
in 5.0 since it will always betrue
whenssl_minimal_tls_version_enforced
is set to1.2
PR Checklist
For example: “
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
Testing
In progress
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_postgresql_server
- deprecatessl_enforcement_enabled
andssl_minimal_tls_version_enforced
no longer accpetsTLSEnforcementDisabled
,TLS1_0
orTLS1_1
as a value in 5.0 [GH-00000]This is a (please select all that apply):
Related Issue(s)
Note
If this PR changes meaningfully during the course of review please update the title and description as required.