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_scc_profile_attachment does not update attachment parameters #5535

Closed
pauljegouic opened this issue Jul 29, 2024 · 7 comments · Fixed by #5551
Closed

ibm_scc_profile_attachment does not update attachment parameters #5535

pauljegouic opened this issue Jul 29, 2024 · 7 comments · Fixed by #5551

Comments

@pauljegouic
Copy link

Hello there,

Used Terraform Provider versions:

- terraform.io/builtin/terraform is built in to Terraform
- Reusing previous version of ibm-cloud/ibm from the dependency lock file
- Reusing previous version of hashicorp/random from the dependency lock file
- Reusing previous version of hashicorp/time from the dependency lock file
- Using previously-installed hashicorp/random v3.6.2
- Using previously-installed hashicorp/time v0.12.0
- Using previously-installed ibm-cloud/ibm v1.67.1

When using : ibm_scc_profile_attachment it successfully does the creation, for the attachment parameters, but does not update the attachment_parameters value.

image

Expected: when I change a value of the attachment parameter, the change is applied to the attachment.

@hkantare

@ocofaigh
Copy link
Contributor

cc @tyao117

@sailajaperumalla
Copy link

SCC reference ticket : https://github.ibm.com/project-fortress/pm/issues/17605

@tyao117
Copy link
Contributor

tyao117 commented Jul 30, 2024

@ocofaigh and @pauljegouic won't be able to start work on this issue until August 2nd.

@pauljegouic
Copy link
Author

That's ok from my prospective.

@tyao117
Copy link
Contributor

tyao117 commented Aug 6, 2024

I believe to have found the source the problem. The function hashAttachmentParameters.

@pauljegouic you can verify the link is the source of the issue using the env var TF_LOG. You will not see a PUT request.

@pauljegouic
Copy link
Author

Not sure what you want me to do. Can't you do this debug on your side ? @tyao117

I can share the logs if needed on Slack, but not here. As you mentionned, there's not PUT request in my logs.

@tyao117
Copy link
Contributor

tyao117 commented Aug 6, 2024

Yes, i am doing debugging on my side, but i need to confirm that you are experiencing the same behavior. Delivering a fix that you are not experiencing would not be productive, would it?

Thanks for confirming the PUT request not being in the logs. The behavior aligns with what I am seeing as well. I am working on the fix while also updating the tests as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants