You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2022. It is now read-only.
This issue was originally opened by @nagulako as hashicorp/terraform-provider-opc#11. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
0.9.5
Affected Resource(s)
opc_instance
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
As an alternative to updating sec_lists in the instance resource definition, a new sec_list can be added to a running instance using the opc_compute_security_association resource.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue was originally opened by @nagulako as hashicorp/terraform-provider-opc#11. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
0.9.5
Affected Resource(s)
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Expected Behavior
When a sec_list is added to the instance - it should be added to the Instance.
Actual Behavior
It does not. Terraform does not validate if the Sec List already exists on the instance or if it is added.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Important Factoids
This is running on OPC IaaS compute
References
No
The text was updated successfully, but these errors were encountered: