Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform Version and Provider Version
OCI plugin version 5.21.0
Affected Resource(s)
oci_database_data_guard_association
Expected Behavior
When creating a DBCS resource in a non DNS enabled subnet, the domain attribute has to be used to provide a domain name for the DBCS node.
While this attributes exists in the oci_database_db_system resource, it does not exists in the oci_database_data_guard_association resource and when creating a standby database in a non DNS enabled subnet the creation fails with the error that the domain cannot be null (so it's also not inherited from the primary DBCS system).
Community Note
Terraform Version and Provider Version
OCI plugin version 5.21.0
Affected Resource(s)
oci_database_data_guard_association
Expected Behavior
When creating a DBCS resource in a non DNS enabled subnet, the domain attribute has to be used to provide a domain name for the DBCS node. While this attributes exists in the oci_database_db_system resource, it does not exists in the oci_database_data_guard_association resource and when creating a standby database in a non DNS enabled subnet the creation fails with the error that the domain cannot be null (so it's also not inherited from the primary DBCS system).
The underlying API does has the domain attribute in the CreateDataGuardAssociationToExistingDbSystemDetails configuration item And also the Web Console exposes this attribute field
So we expect the TerraForm resource to also expose the domain attribute to avoid deployments to fail We also created SR 3-35008132171 for this.
Actual Behavior
Deployment fails because the domain name is null
Steps to Reproduce
Important Factoids
References