-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: existing scc instance for DA #106
base: main
Are you sure you want to change the base?
Conversation
Do we need to add an existing scc instance to permanent resources and specify it here? |
@jor2 no we don't need a permanent SCC instance. One can be provisioned in https://github.com/terraform-ibm-modules/stack-ibm-core-security-services/tree/main/tests/resources as part of the test if needed |
/run pipeline |
/run pipeline |
/run pipeline |
…-ibm-core-security-services into existing-scc
/run pipeline |
/run pipeline |
/run pipeline |
1 similar comment
/run pipeline |
failure related to this again it seems, retrying |
/run pipeline |
@jor2 hoping to do a release this week for core security services stack DA. Do we keep hitting the same issue in the tests here? |
yes, same issue we thought solved before.
|
adding sleep to scc-da terraform-ibm-modules/terraform-ibm-scc-da#184 |
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
Description
Enable skipping SCC provisioning
terraform-ibm-modules/stack-retrieval-augmented-generation#131
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
enable skipping SCC provisioning by providing option for passing existing scc instance id.
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