-
Notifications
You must be signed in to change notification settings - Fork 2
refactor: ignoring parameter cloud_monitoring_connected_instance and updating the description. #354
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 |
|
/run pipeline |
|
/run pipeline |
|
🎉 This PR is included in version 1.16.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
| nullable = true | ||
| default = null | ||
| description = "To collect and analyze metrics and security data on hosts using both Monitoring and Workload Protection, pass the CRN of an existing IBM Cloud Monitoring instance to create a connection between instances. Both instances must be in the same region. [Learn more](https://www.ibm.com/products/cloud-monitoring)" | ||
| description = "To collect and analyze metrics and security data on hosts using both Monitoring and Workload Protection, pass the CRN of an existing IBM Cloud Monitoring instance to create the connection. Once the connection is created, the Monitoring instance CRN cannot be changed. Learn more](https://www.ibm.com/products/cloud-monitoring)" |
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.
You are missing the opening bracket
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.
Also can we point to a better link - thats too generic. Is there any doc that has info abut this topic (connecting instances)
| cloud_monitoring_connected_instance : var.cloud_monitoring_instance_crn | ||
| cloud_monitoring_connected_instance = var.cloud_monitoring_instance_crn | ||
| } | ||
| lifecycle { |
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.
always leave a code comment as to why your adding a lifecycle ignore
Description
Added clarification to the cloud_monitoring_instance_crn variable description in both the module and DA to state that once the Monitoring Instance CRN is connected to the Security and Compliance Center Workload Protection service, it cannot be modified or updated. for issue https://github.ibm.com/GoldenEye/issues/issues/16321.
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