Skip to content
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 doesn't have the right value for s3_endpoint_public when endpoint_type is set to private #5404

Closed
akocbek opened this issue May 31, 2024 · 5 comments
Labels
service/Object Storage Issues related to Cloud Object Storage service/Resource Management Issues related to Resource Manager or Resource controller Issues

Comments

@akocbek
Copy link

akocbek commented May 31, 2024

Community Note

  • 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

When we create ibm_cos_bucket resource using ibm provider and we set endpoint_type to private then s3_endpoint_public has private endpoint instead of public.

"s3_endpoint_direct" = "s3.direct.us-south.cloud-object-storage.appdomain.cloud"
"s3_endpoint_private" = "s3.private.us-south.cloud-object-storage.appdomain.cloud"
"s3_endpoint_public" = "s3.private.us-south.cloud-object-storage.appdomain.cloud"

Terraform CLI and Terraform IBM Provider Version

Affected Resource(s)

  • ibm_cos_bucket

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "ibm_resource_group" "resource_group" {
  name     = "a-test-rg"
}


resource "ibm_resource_instance" "cos_instance" {
  name              = "a-test-cos-instance"
  resource_group_id = resource.ibm_resource_group.resource_group.id
  service           = "cloud-object-storage"
  plan              = "standard"
  location          = "global"
}

resource "ibm_cos_bucket" "cos_bucket_test" {
  resource_instance_id  =  resource.ibm_resource_instance.cos_instance.id
  bucket_name           = "a-test-cos-bucket"
  region_location       = "us-south"
  endpoint_type = "private"
}

output ibm_cos_bucket {
    value = ibm_cos_bucket.cos_bucket_test
}

Debug Output

https://gist.github.com/akocbek/4e181df0042eb670f158461e55c24f4e

Panic Output

Expected Behavior

s3_endpoint_public output variable should have public endpoint, when endpoint_type input variable is set to private

Actual Behavior

s3_endpoint_public output variable has private endpoint, when endpoint_type input variable is set to private

Steps to Reproduce

  1. terraform apply

Important Factoids

References

  • #0000
@github-actions github-actions bot added service/Object Storage Issues related to Cloud Object Storage service/Resource Management Issues related to Resource Manager or Resource controller Issues labels May 31, 2024
@IBM-diksha
Copy link
Collaborator

@akocbek We are looking into this.
Thank you.

@IBM-Deeksha
Copy link
Contributor

@akocbek
We have investigated the issue and have identified the root cause.
Our team is currently working on a solution. We'll keep you updated on our progress.

@IBM-Deeksha
Copy link
Contributor

IBM-Deeksha commented Jun 18, 2024

Fix delivered in beta release. Thank you for reporting.

@IBM-diksha
Copy link
Collaborator

Closing the Issue as the fix has been delivered.
Thank you.

@akocbek
Copy link
Author

akocbek commented Jul 1, 2024

@IBM-Deeksha thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/Object Storage Issues related to Cloud Object Storage service/Resource Management Issues related to Resource Manager or Resource controller Issues
Projects
None yet
Development

No branches or pull requests

3 participants