IBM-Cloud / terraform-provider-ibm

https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs
Mozilla Public License 2.0
341 stars 669 forks source link

ibm_scc_profile_attachment does not update attachment parameters #5535

Closed pauljegouic closed 2 months ago

pauljegouic commented 3 months ago

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 commented 3 months ago

cc @tyao117

sailajaperumalla commented 3 months ago

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

tyao117 commented 3 months ago

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

pauljegouic commented 3 months ago

That's ok from my prospective.

tyao117 commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

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.