When the module is used with the existing Event Noitications instance CRN, the COS and KMS parameters should be ignored and the module should not try to provision the related resources (COS instances, buckets, S2S authorizations, KMS keys)
Currently it creates all of the above even though it cannot be connected to the existing EN instance.
Affected modules
*
Terraform CLI and Terraform provider versions
Terraform version:
Provider version:
Terraform output
Debug output
Expected behavior
Actual behavior
Steps to reproduce (including links and screen captures)
Run terraform apply
Anything else
By submitting this issue, you agree to follow our Code of Conduct
ocofaigh
commented
4 hours ago
When the module is used with the existing Event Noitications instance CRN, the COS and KMS parameters should be ignored and the module should not try to provision the related resources (COS instances, buckets, S2S authorizations, KMS keys)
Currently it creates all of the above even though it cannot be connected to the existing EN instance.
Affected modules
*
Terraform CLI and Terraform provider versions
Terraform output
Debug output
Expected behavior
Actual behavior
Steps to reproduce (including links and screen captures)
terraform applyAnything else
By submitting this issue, you agree to follow our Code of Conduct