-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ibm_scc_instance_settings
is failing with Invalid address to set: []string{"event_notifications", "0", "source_description"}
#5817
ibm_scc_instance_settings
is failing with Invalid address to set: []string{"event_notifications", "0", "source_description"}
#5817
Comments
This also impact terraform destroy. So once a consumer hits this, they can't even destroy the resources |
FYI, not able to reproduce in us-south. Above logs are from eu-de |
I started facing this issue in this minimal standalone sample Blocking issue... |
Provider 1.71.3 fixes the issue, but introduced a new error
Adding the source_name fixes the issue. The doc should reflect that this attribute is required (not optional as mentioned)
|
@lionelmace yea, I just left that comment in the PR -> #5818 (comment) Its good that the provider is catching it, but I think the descrption could be clearer (cc @tyao117 @hkantare ) |
…/terraform-provider-ibm#5817)). It is now required to pass a value for new input `en_source_name` when passing a value for `en_instance_crn`. There is also now an optional input `en_source_description`. These changes require IBM provider version >=1.71.3 (#198)
Community Note
Terraform CLI and Terraform IBM Provider Version
tf 1.9.2
ibm provider 1.71.2
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
scc-debug.txt
Panic Output
Expected Behavior
No error
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: