Closed Soaib024 closed 4 months ago
/run pipeline
/run pipeline
/run pipeline
Changes:
core-security-services-en
version_locator
to latest (v1.5).core-security-observability
to core-security-services-en
.core-security-services-en
as that will be created by core-security-observability
.core-security-services-en
is already using KMS created by core-security-services-kms
, so no changes required.Note:
The names of the stack elements are:
1-core-security-services-kms
3-core-security-observability
2-core-security-services-en
Now, EN
is dependent on observability
, so should we change the name to 2-core-security-observability
and 3-core-security-services-en
to reflect the actual order of the stack? @ocofaigh @tyao117
@Soaib024 I created an issue to update the member names: https://github.com/terraform-ibm-modules/stack-ibm-core-security-services/issues/34
However for this PR, lets just keep current naming and rename like you mentioned:
2-core-security-observability
3-core-security-services-en
We also need to update the diagram here to show the new COS flows for EN
/run pipeline
/run pipeline
/run pipeline
/run pipeline
/run pipeline
/run pipeline
:tada: This PR is included in version 0.2.0 :tada:
The release is available on:
v0.2.0
Your semantic-release bot :package::rocket:
used EN latest version_locator and passed cos instance created by obs DA to EN
Description
https://github.com/terraform-ibm-modules/stack-ibm-core-security-services/issues/9
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