-
Notifications
You must be signed in to change notification settings - Fork 0
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
bucket_endpoint is not exposed in SCC module #127
Comments
Looking into what the default endpoint is |
instance_settings.object_storage.bucket_endpoint is an empty string by default. |
@ocofaigh do you want to expose it? |
@kierramarie do what endpoint is used to communicate with the COS bucket if its not specified? public, private, direct? |
@ocofaigh it looks like the default is public |
@kierramarie yea lets expose it as optional - make sure to specify in the description that is not passed, it defaults to use public endpoint |
This will then have to be backported to the SCC DA |
Will do. |
Seems its an issue with the docs, which is already being tracked here -> IBM-Cloud/terraform-provider-ibm#5110 |
ibm_scc_instance_settings
seems to have a bucket_endpoint option that we are not using in the module.The provider documentation is terrible here, but I'm assuming that if not value passed, its defaulting to public endpoint? Can we find this out - we may need to expose the ability for users to override the endpoint if they have public endpoint disabled for buckets.
The text was updated successfully, but these errors were encountered: