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
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
ibm_iam_trusted_profile_identity
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
# Copy-paste your Terraform configurations here - for large Terraform configs,# please share a link to the ZIP file.
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
#0000
The text was updated successfully, but these errors were encountered:
IAM team responded internally to say they are both required as per the documentation: https://cloud.ibm.com/apidocs/iam-identity-token-api#set-profile-identity. The difference between them is that identity_type is a path parameter and type is a body parameter. They can't be different values, they need to be same.
With this in mind, I think the provider should be updated to just ask for a single arg, and then pass both args to the api call in the code. @Somchavan This will be a much better user experience for consumers of the provider. Can it be implemented?
Looking at the docs for ibm_iam_trusted_profile_identity there seems to be 2 args that are the same. Is this a bug?
Community Note
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: