fix: adding iam engine option to SM and prefix to SCC

iamar7 commented 1 week ago

Description

Resolves: https://github.com/terraform-ibm-modules/stack-retrieval-augmented-generation/issues/12, https://github.com/terraform-ibm-modules/stack-retrieval-augmented-generation/issues/130

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (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:

/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

iamar7 commented 1 week ago

/run pipeline

iamar7 commented 1 week ago

/run pipeline

iamar7 commented 1 week ago

/run pipeline

ocofaigh commented 6 days ago

@daniel-butler-irl If this stack is being updated to consume the core security services stack, then the change to add iam_engine_enabled should come in that stack first right?

iamar7 commented 6 days ago

@daniel-butler-irl If this stack is being updated to consume the core security services stack, then the change to add iam_engine_enabled should come in that stack first right?

core-security-services-stack PR ~> https://github.com/terraform-ibm-modules/stack-ibm-core-security-services/pull/70

iamar7 commented 1 day ago

/run pipeline

terraform-ibm-modules / stack-retrieval-augmented-generation