Skip to content

Conversation

@arya-girish-k
Copy link
Contributor

Description

https://github.ibm.com/GoldenEye/issues/issues/14605

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k arya-girish-k marked this pull request as ready for review July 9, 2025 04:44
Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think all the comment I left in terraform-ibm-modules/terraform-ibm-cloud-monitoring#51 are also applicable in this Pr - please update

@arya-girish-k
Copy link
Contributor Author

I think all the comment I left in terraform-ibm-modules/terraform-ibm-cloud-monitoring#51 are also applicable in this Pr - please update

Updated.

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k
Copy link
Contributor Author

/run pipeline

Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see comments

}

variable "metadata_region_primary" {
description = "Storage location for target, route, and settings metadata in your IBM Cloud account. To store all configuration metadata in a single region, set this value explicitly. For new accounts, creating targets and routes will fail until `metadata_region_primary` is set. If set to `null`, no change is made to the current value."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For new accounts, creating targets and routes will fail until metadata_region_primary is set.

^ Are you sure about this?? I thought this was only for Metrics routing? Please test and confirm

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this description,since it is an required string ,I have provided default_value="us-south"

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k arya-girish-k requested a review from ocofaigh July 23, 2025 07:18
@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k
Copy link
Contributor Author

Tests fails with this error and unrelated to my change,Investigating the same:

         2025/07/23 09:48:55 Terraform apply | 	status code: 400, request id: 333efacb-a894-410d-a5df-3ba6f65796d0, host id: 
         2025/07/23 09:48:55 Terraform apply | 
         2025/07/23 09:48:55 Terraform apply |   with module.cos_bucket[0].module.buckets["at-fc-upg-aep-at-events-cos-bucket"].ibm_cos_bucket.cos_bucket[0],
         2025/07/23 09:48:55 Terraform apply |   on .terraform/modules/cos_bucket/main.tf line 122, in resource "ibm_cos_bucket" "cos_bucket":
         2025/07/23 09:48:55 Terraform apply |  122: resource "ibm_cos_bucket" "cos_bucket" {
         2025/07/23 09:48:55 Terraform apply | 
         2025/07/23 09:48:55 Terraform apply | ---
         2025/07/23 09:48:55 Terraform apply | id: terraform-d2853781
         2025/07/23 09:48:55 Terraform apply | summary: "InvalidRequest: Server Side Encryption with hs-crypto is not
         2025/07/23 09:48:55 Terraform apply | enabled.\n\tstatus
         2025/07/23 09:48:55 Terraform apply |   code: 400, request id: 333efacb-a894-410d-a5df-3ba6f65796d0, host id: "
         2025/07/23 09:48:55 Terraform apply | severity: error
         2025/07/23 09:48:55 Terraform apply | resource: ibm_cos_bucket
         2025/07/23 09:48:55 Terraform apply | operation: create
         2025/07/23 09:48:55 Terraform apply | component:
         2025/07/23 09:48:55 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
         2025/07/23 09:48:55 Terraform apply |   version: 1.80.3
         2025/07/23 09:48:55 Terraform apply | ---
         2025/07/23 09:48:55 Terraform apply | 
         2025/07/23 09:48:55 Terraform APPLY error: Terraform APPLY errorexit status 1
         2025/07/23 09:48:55 Could not execute job: Error : Terraform APPLY errorexit status 1
         ```
         

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k
Copy link
Contributor Author

Tests fails with this error and unrelated to my change,Investigating the same:

         2025/07/23 09:48:55 Terraform apply | 	status code: 400, request id: 333efacb-a894-410d-a5df-3ba6f65796d0, host id: 
         2025/07/23 09:48:55 Terraform apply | 
         2025/07/23 09:48:55 Terraform apply |   with module.cos_bucket[0].module.buckets["at-fc-upg-aep-at-events-cos-bucket"].ibm_cos_bucket.cos_bucket[0],
         2025/07/23 09:48:55 Terraform apply |   on .terraform/modules/cos_bucket/main.tf line 122, in resource "ibm_cos_bucket" "cos_bucket":
         2025/07/23 09:48:55 Terraform apply |  122: resource "ibm_cos_bucket" "cos_bucket" {
         2025/07/23 09:48:55 Terraform apply | 
         2025/07/23 09:48:55 Terraform apply | ---
         2025/07/23 09:48:55 Terraform apply | id: terraform-d2853781
         2025/07/23 09:48:55 Terraform apply | summary: "InvalidRequest: Server Side Encryption with hs-crypto is not
         2025/07/23 09:48:55 Terraform apply | enabled.\n\tstatus
         2025/07/23 09:48:55 Terraform apply |   code: 400, request id: 333efacb-a894-410d-a5df-3ba6f65796d0, host id: "
         2025/07/23 09:48:55 Terraform apply | severity: error
         2025/07/23 09:48:55 Terraform apply | resource: ibm_cos_bucket
         2025/07/23 09:48:55 Terraform apply | operation: create
         2025/07/23 09:48:55 Terraform apply | component:
         2025/07/23 09:48:55 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
         2025/07/23 09:48:55 Terraform apply |   version: 1.80.3
         2025/07/23 09:48:55 Terraform apply | ---
         2025/07/23 09:48:55 Terraform apply | 
         2025/07/23 09:48:55 Terraform APPLY error: Terraform APPLY errorexit status 1
         2025/07/23 09:48:55 Could not execute job: Error : Terraform APPLY errorexit status 1
         ```
         

Pipeline is failing in jp-osa region as jp-osa region does not support COS association with HPCS and hence we are facing that issue with COS bucket creation in JP-OSA region.So simply hard coded the region which supports cos association with HPCS

Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see comments

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@ocofaigh ocofaigh merged commit 9f536bf into main Jul 25, 2025
2 checks passed
@ocofaigh ocofaigh deleted the account-routing branch July 25, 2025 14:32
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@@ -0,0 +1,3 @@
{
"ibmcloud_api_key": $VALIDATION_APIKEY"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missed this typo - fixed in #60

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants