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

fix: correct the resource name being printed in ibm_en_integration logging #6037

Merged
merged 1 commit into from
Mar 7, 2025

Conversation

ocofaigh
Copy link
Contributor

@ocofaigh ocofaigh commented Mar 3, 2025

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment 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 pull request followers and do not help prioritize the request

The ibm_en_integration resource is printing ibm_en_integration_cos instead of instead of ibm_en_integration in its logging. For example:

 2025/03/03 11:00:46 Terraform apply | Error: ---
 2025/03/03 11:00:46 Terraform apply | id: terraform-afa76cbf
 2025/03/03 11:00:46 Terraform apply | summary: 'ReplaceIntegrationWithContext failed: Gateway Timeout'
 2025/03/03 11:00:46 Terraform apply | severity: error
 2025/03/03 11:00:46 Terraform apply | resource: ibm_en_integration_cos
 2025/03/03 11:00:46 Terraform apply | operation: create
 2025/03/03 11:00:46 Terraform apply | component:
 2025/03/03 11:00:46 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
 2025/03/03 11:00:46 Terraform apply |   version: 1.75.2
 2025/03/03 11:00:46 Terraform apply | ---

and
image

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

@hkantare hkantare merged commit 158e1ae into IBM-Cloud:master Mar 7, 2025
1 check passed
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 this pull request may close these issues.

2 participants