Closed lechnerc77 closed 1 month ago
Drift detection error is okay, as the test fixtures for the resources and data sources had to be re-recorded
In the files examples/resources/btp_globalaccount_security_settings/resource.tf
and examples/resources/btp_subaccount_security_settings/resource.tf
, the attribute iframe_domains
is a shown as a list although the attribute is a string as per the schema.
In the file internal/provider/datasource_globalaccount_security_settings.go
and internal/provider/datasource_globalaccount_security_settings_test.go
, the attribute iframe_domains
is configured as Optional as well as Computed. This is being reflected in the documentation as well.
In the files
examples/resources/btp_globalaccount_security_settings/resource.tf
andexamples/resources/btp_subaccount_security_settings/resource.tf
, the attributeiframe_domains
is a shown as a list although the attribute is a string as per the schema.
Resolved
In the file
internal/provider/datasource_globalaccount_security_settings.go
andinternal/provider/datasource_globalaccount_security_settings_test.go
, the attributeiframe_domains
is configured as Optional as well as Computed. This is being reflected in the documentation as well.
Fixed
Drift detection can be ignored as fixtures were re-recorded
Tested out changes, everything works fine
Purpose
iframe_domains
was added to the resources and data sources for security settings to be in sync with the BTP CLIDoes this introduce a breaking change?
Pull Request Type
What kind of change does this Pull Request introduce?
How to Test
What to Check
Verify that the following are valid:
Other Information
Due to the
make fmt
some files have been formated that are not subject to the changeChecklist for reviewer
The following organizational tasks must be completed before merging this PR: