-
Notifications
You must be signed in to change notification settings - Fork 0
Add Event routing account settings variation #48
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
Conversation
|
/run pipeline |
There was a problem hiding this 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
Updated. |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments
solutions/event-routing-account-settings/catalogValidationValues.json.template
Outdated
Show resolved
Hide resolved
| } | ||
|
|
||
| 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." |
There was a problem hiding this comment.
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_primaryis set.
^ Are you sure about this?? I thought this was only for Metrics routing? Please test and confirm
There was a problem hiding this comment.
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"
|
/run pipeline |
|
/run pipeline |
|
Tests fails with this error and unrelated to my change,Investigating the same: |
|
/run pipeline |
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments
Co-authored-by: Conall Ó Cofaigh <[email protected]>
|
/run pipeline |
|
/run pipeline |
|
🎉 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" | |||
There was a problem hiding this comment.
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
Description
https://github.ibm.com/GoldenEye/issues/issues/14605
Release required?
x.x.X)x.X.x)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:
Checklist for reviewers
For mergers