-
Notifications
You must be signed in to change notification settings - Fork 689
CS4273275 - [CLOUDANT] [TERRAFORM v1.77.1] [TrustedProfile Integration] #6181
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
Comments
The fix provided was only part of "ibm_database" datasource. The fix for ibm_cloudant will be provided in upcoming releases |
Client is trying to incorporate 'trusted-profile' integration for their coding logic based on: -> - https://registry.terraform.io/providers/IBM-Cloud/ibm/1.77.1/docs/data-sources/iam_trusted_profile I was adviced in another thread (https://github.ibm.com/compose/compose/issues/50039), as per the comment of @guruprasad0110:
Please have a look and let us know what needs to be done. |
@hkantare Is there an estimate ETA for the fix for the <ibm_cloudant> data source? |
@hkantare can you kindly advice? |
We will be planning to fix this issue as part of this month end release |
got below updated from cx -- they need a date
|
The PR is in review process |
My team has tested the new version (v1.77.1) of the terraform-provider-ibm, and we are still encountering the same error related to the trusted profile token.
I also reviewed the release notes for v1.77.1, and I do not see any mention of this issue being addressed. This leads me to believe that the fix may not have been included in this release.
If the fix had been included, I would have expected it to be referenced in the release notes—similar to how the ICD issue was clearly mentioned in v1.76.2 release notes.
Below are the logs we observed during our testing with v1.77.1:
Could someone please confirm whether this issue has already been addressed or if a fix is planned for an upcoming release?
This is becoming increasingly critical, as we have a customer who is currently blocked due to this issue. We need a resolution on a high-priority basis.
We are happy to connect directly with the individual or team working on this so that we can accelerate progress and get the issue addressed as quickly as possible.
Thanks again!
The text was updated successfully, but these errors were encountered: