- Notifications
You must be signed in to change notification settings - Fork 13
fully configurable #255
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
fully configurable #255
Conversation
| Variation used for "Accounts Infrastructure Base" is |
|
| Updated elasticsearch_version to 8.15 from 8.12 |
| focuses on the |
ocofaigh left a comment
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
| @rajatagarwal-ibm similar test updates also needed in pr_test.go |
ocofaigh left a comment
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.
- Your code doesn't seem to handle the
existing_resource_group_nameuse case. Current DA supports this, but defaults to creating new resource groups. We may want to revisit this and refactor based on best user experience. - Rename
existing_event_notification_instance_crn->existing_event_notifications_instance_crn - Rename
existing_discovery_instance->existing_discovery_instance_crn - Rename
existing_governance_instance->existing_governance_instance_crn - Rename
existing_studio_instance->existing_studio_instance_crn - Update
prefixdescription to align the this guidance, and remove the default value - Rename the output
event_notification_instance_crn->event_notifications_instance_crn - Rename the output
event_notification_instance_name->event_notifications_instance_name - Rename the output
event_notifications_instance_guid->event_notifications_instance_guid - We should be able to support more regions than
us-southandeu-de? I think some watson services were not supported in all regions, but we should check now and update
ocofaigh left a comment
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.
Just noticed the diagram needs an update - it still references the legacy SCC
| /run pipeline |
ocofaigh left a comment
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.
Update .catalog-onboard-pipeline.yaml with new variation name
| /run pipeline |
| /run pipeline |
| /run pipeline |
| /run pipeline |
| /run pipeline |
1 similar comment
| /run pipeline |
| /run pipeline |
| /run pipeline |
| 🎉 This PR is included in version 4.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |

Description
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