Addon dependency config for elasticsearch #482
Conversation
ibm_catalog.json
Outdated
| "reference_version": true | ||
| } | ||
| ], | ||
| "version": "v1.10.1", |
There was a problem hiding this comment.
Are you supposed to pinpoint the version? I know we were doing this for Core PaaS (and surround too), but not sure if that's applicable to ICD modules too.
There was a problem hiding this comment.
We need to be careful here because SCC-WP and App Config will have their own dependencies, and we need to ensure we lock to the same versions they are locked to when adding the same dependencies to this DA (eg KP, Observability, SM etc)
There was a problem hiding this comment.
In order to catch such mismatched version we should add the addons testing in this same PR. See Key Protect or Observability tests for reference
|
This will need rebasing on #181 when it is merged to get the tests to pass. |
whoffler
force-pushed
the
sccWorkloadProtectionDependency
branch
6 times, most recently
from
015fd67 to
4f4a788
Compare
whoffler
changed the title
whoffler
force-pushed
the
sccWorkloadProtectionDependency
branch
3 times, most recently
from
ce1d29d to
8919e35
Compare
|
/run pipeline |
3 similar comments
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
whoffler
force-pushed
the
sccWorkloadProtectionDependency
branch
from
f8270d6 to
b5e106a
Compare
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
Description
for issue - https://github.ibm.com/GoldenEye/issues/issues/13577
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