-
Notifications
You must be signed in to change notification settings - Fork 1
feat: update few DAs references with new values #19
Conversation
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.
Ref for elastic_instance_crn may need to be fixed. Also wonder if fixes for #15 can be added.
|
added elastic_instance_crn |
|
/run pipeline |
|
/run pipeline |
1 similar comment
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
2 similar comments
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
stack_definition.json
Outdated
| { | ||
| "name": "elasticsearch_port", | ||
| "value": "ref:./members/3b - Databases for Elasticsearch/outputs/port" | ||
| "value": " ref:../3b - Databases for Elasticsearch/outputs/port" |
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.
@akocbek - I think you have an extra leading space
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.
@in-1911 good catch, thanks
|
/run pipeline |
|
🎉 This issue has been resolved in version 0.3.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
…ort to use existing watsonx services</br> - ES output is used as an input of sample app config DA</br> - watsonx discovery is disabled by default</br> - KMS instances is passed to watsonx and sample app config DA</br> - added support to use existing ES instance</br> - updated the version locator for DAs
…ort to use existing watsonx services</br> - ES output is used as an input of sample app config DA</br> - watsonx discovery is disabled by default</br> - KMS instances is passed to watsonx and sample app config DA</br> - added support to use existing ES instance</br> - updated the version locator for DAs
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