Bug Description
Getting error "400-InvalidParameter, Domain name cannot be null"
while creating DB System (DBCS) using CD3 toolkit via Jenkins.
Root Cause
The DBSystems-VM-BM Excel sheet does not have a "domain" column.
CD3 generates the .auto.tfvars without the domain parameter,
but the OCI Terraform provider now requires domain as a mandatory
field for LaunchDbSystem API.
Steps to Reproduce
- Fill DBSystems-VM-BM sheet in CD3 Excel template
- Run CD3 toolkit with "Create Resources" workflow for Database
- Run Terraform apply via Jenkins
- Error: 400-InvalidParameter, Domain name cannot be null
Expected Behavior
CD3 should include "domain" column in DBSystems-VM-BM sheet and
generate domain parameter in the .auto.tfvars file automatically
using subnet DNS label + VCN DNS label.
Environment
- CD3 Toolkit Version: (మీ version రాయండి)
- OCI Terraform Provider Version: 7.19.x
- Workflow: Jenkins
Error Message
Error: 400-InvalidParameter, Domain name cannot be null.
Provider version: 7.19.x
Bug Description
Getting error "400-InvalidParameter, Domain name cannot be null"
while creating DB System (DBCS) using CD3 toolkit via Jenkins.
Root Cause
The DBSystems-VM-BM Excel sheet does not have a "domain" column.
CD3 generates the .auto.tfvars without the domain parameter,
but the OCI Terraform provider now requires domain as a mandatory
field for LaunchDbSystem API.
Steps to Reproduce
Expected Behavior
CD3 should include "domain" column in DBSystems-VM-BM sheet and
generate domain parameter in the .auto.tfvars file automatically
using subnet DNS label + VCN DNS label.
Environment
Error Message
Error: 400-InvalidParameter, Domain name cannot be null.
Provider version: 7.19.x