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
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 other comments that do not add relevant new information or questions, 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
Notice that the "cis_id" above is not a CRN, but guid.
Other resources using the same syntax to get the cis_id resolve to:
cis_id = "crn:v1:bluemix:public:internet-svcs:global:a/b2025f2345dc4e2c9477a5b4c0428805:2f70cb31-7c7e-4271-92cb-4b7b4b5c8737::"
Expected Behavior
Should have created an ibm_cis_rate_limit rule associated with the cis instance.
Actual Behavior
terraform apply resulted in:
ibm_cis_rate_limit.ratelimit[0]: Creating...
...
Error: cis_id or zone_id not passed
on cis.tf line 174, in resource "ibm_cis_rate_limit" "ratelimit":
174: resource "ibm_cis_rate_limit" "ratelimit" {
Steps to Reproduce
terraform apply
I also tried modifying the tf files and hard coding the full cis_id crn. The plan then showed:
Error: cis_id or zone_id not passed
on cis.tf line 175, in resource "ibm_cis_rate_limit" "ratelimit":
175: resource "ibm_cis_rate_limit" "ratelimit" {
I also tried creating the object in the Browser and then doing an import, which worked
terraform import ibm_cis_rate_limit.ratelimit 7e8e2e0c8c5741aeb6336710cdf3e814:f3d51dd43ff9b463a270d04e0d6ffcc4:crn:v1:bluemix:public:internet-svcs:global:a/b2025f2345dc4e2c9477a5b4c0428805:2f70cb31-7c7e-4271-92cb-4b7b4b5c8737::
var.unique_id
Enter a value: ksb-docker
var.vpc_load_balancer_address
Address of the vpc load balancer to use in the origin
Enter a value: 1.2.3.4
ibm_cis_rate_limit.ratelimit: Importing from ID "7e8e2e0c8c5741aeb6336710cdf3e814:f3d51dd43ff9b463a270d04e0d6ffcc4:crn:v1:bluemix:public:internet-svcs:global:a/b2025f2345dc4e2c9477a5b4c0428805:2f70cb31-7c7e-4271-92cb-4b7b4b5c8737::"...
ibm_cis_rate_limit.ratelimit: Import prepared!
Prepared ibm_cis_rate_limit for import
ibm_cis_rate_limit.ratelimit: Refreshing state... [id=7e8e2e0c8c5741aeb6336710cdf3e814:f3d51dd43ff9b463a270d04e0d6ffcc4:crn:v1:bluemix:public:internet-svcs:global:a/b2025f2345dc4e2c9477a5b4c0428805:2f70cb31-7c7e-4271-92cb-4b7b4b5c8737::]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
ibm_cis_rate_limit.ratelimit[0]: Modifying... [id=7e8e2e0c8c5741aeb6336710cdf3e814:f3d51dd43ff9b463a270d04e0d6ffcc4:crn:v1:bluemix:public:internet-svcs:global:a/b2025f2345dc4e2c9477a5b4c0428805:2f70cb31-7c7e-4271-92cb-4b7b4b5c8737::]
Error: Error in getting correlate from expandRateLimitCorrelate correlate field is empty
on cis.tf line 175, in resource "ibm_cis_rate_limit" "ratelimit":
175: resource "ibm_cis_rate_limit" "ratelimit" {
The text was updated successfully, but these errors were encountered:
Community Note
Terraform CLI and Terraform IBM Provider Version
terraform -v
Terraform v0.13.0
Affected Resource(s)
Terraform Configuration Files
Plan output
Notice that the "cis_id" above is not a CRN, but guid.
Other resources using the same syntax to get the cis_id resolve to:
cis_id = "crn:v1:bluemix:public:internet-svcs:global:a/b2025f2345dc4e2c9477a5b4c0428805:2f70cb31-7c7e-4271-92cb-4b7b4b5c8737::"
Expected Behavior
Should have created an ibm_cis_rate_limit rule associated with the cis instance.
Actual Behavior
terraform apply resulted in:
Steps to Reproduce
terraform apply
I also tried modifying the tf files and hard coding the full cis_id crn. The plan then showed:
But the apply had the same error:
I also tried creating the object in the Browser and then doing an import, which worked
I then tried a plan and apply (the apply failed):
apply:
The text was updated successfully, but these errors were encountered: