Avoid setting service_endpoints default from the plugin #5218
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.
This avoids setting a default value for
service_endpoints
in the Terraform provider plugin. This allows the default to be set by the backend according to the compliance standard in use at the specific region.Users still have the option to specify one of the following values
public
,private
, orpublic-and-private
forservice_endpoints
. If user leavesservice_endpoints
empty, the default value will be set based on the compliance standard in the region where the instance is being created. Generally, if the region is enabled with FS Cloud/ENS High compliance, then the default would be private. Otherwise, the default would be public. During any update, if you leaveservice_endpoints
empty, it will maintain the previously selected value.Community Note