Closed ptesny closed 1 week ago
The repositories are private, so we are not ables to access the code especially of the module under investigation. The Terraform team would need access or you provide the code of the module's main.tf that uses the resource in this issue
The module code is public https://github.com/quovadis-btp/btp-automation/blob/3e47ea9bbdce9cff28b7f1d168dfe84da92f5809/btp-context/bootstrap-context/modules/custom-idp/bootstrap-custom-idp.tf#L158
just mind the gap I have worked around the problem by instructing tf to recycle the resource at every plan/apply run
just remove the lifecycle section to reproduce the reported issue
btp_directory_api_credential
and btp_globalaccount_api_credential
also have the same issuebtp get security/api-credential
does not return the secret of the created api-credentialthank you. Please make sure it works with both secrets and certificates
Is there an existing issue for this?
What version of the Terraform provider are you using?
1.8.0
What version of the Terraform CLI are you using?
1.9.3
What type of issue are you facing
bug report
Describe the bug
After an initial and successful creation of a btp_subaccount_api_credential resource the subsequent planning operation reset the value of the api_credential secret to null. This makes tf choke if the secret is used to compute the access token.
This is an unexpected behaviour and reported as such in the tf trace log
Expected Behavior
One should be able to create a single instance of the btp_subaccount_api_credential resource and be able to run the same tf configuration multiple times
Steps To Reproduce
Full GHA trace log https://github.com/quovadis-btp/btp-boosters/actions/runs/11756380729/job/32752461363
User's Role Collections
No response
Add screenshots to help explain your problem
and then further on...
Additional context
Full GHA trace log https://github.com/quovadis-btp/btp-boosters/actions/runs/11756380729/job/32752461363