-
Notifications
You must be signed in to change notification settings - Fork 676
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_cos_bucket created with endpoint_type = "public" regardless of the actual setting #5935
Comments
Hi @baal-lgln , we are looking into this issue and will get back to you. |
Hi @baal-lgln, thanks for reaching out. |
I made some more tests.
We don't use a endpoints.json config file or any other environment variables. I didn't mention that the buckets were already created successfully in the past. It seems I'm able to create a bucket with
But after successful creation I can't change the
Is this intentional? The docs don't say anything about changing the endpoint_type after creation. When I want to create a new bucket with a private endpoint_type I get an error even though i'm connected to a IBM VPN or my IP adress is added to the correct Context Based Restriction Rule:
|
Community Note
Terraform CLI and Terraform IBM Provider Version
Terraform v1.9.2
on darwin_arm64
Affected Resource(s)
Terraform Configuration Files
I am provisioning a ibm_cos_bucket and want to use direct or private endpoint option.
Debug Output
Panic Output
Expected Behavior
A ibm_cos_bucket with
endpoint_type = "private"
.Actual Behavior
A ibm_cos_bucket with
endpoint_type = "public"
:Steps to Reproduce
terraform apply the above configuration with endpoint type private
Important Factoids
References
I was able find some solved issues with similar problems:
s3_endpoint_public
whenendpoint_type
is set to private #5404The text was updated successfully, but these errors were encountered: