feat: add new variations without sample app

[imprateeksh]

Description

fixes: #247

This PR addresses issue to include two new variations without sample app and devops alm.
Also, addressing two other issues to update the diagram and to document the known limitation with the RAG stack.

Release required?

• No release
• 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.

[imprateeksh]

[imprateeksh]

Seeing Projects failure while adding to catalog - https://ibm-cloudplatform.slack.com/archives/C03554X40G3/p1762856522691989

[ocofaigh]

@imprateeksh can you get this up to date with the changes that went into v5.0.1 please?

[imprateeksh]

Unable to test - Getting failures while adding to new project or using existing project.

[ocofaigh]

@imprateeksh I thought even though you hit that error in the UI, the project still gets created?

[imprateeksh]

@imprateeksh I thought even though you hit that error in the UI, the project still gets created?

Yes that is correct observation Conall. Only difference is last time there was no configuration added and this time we do have the configuration. I am already checking that.

[imprateeksh]

Deployment is successful (error message is wrongly shown) -

[imprateeksh]

In Progress - Metadata should be same for the ibmcatalog.json present here and for quickstart variation from cloud-native-ai repo.

[ocofaigh]

Few comments. Also the diagram colours seem odd. Do they show like this for you? Also you should add App Configuration in the same line as SCC-WP

[imprateeksh]

Few comments. Also the diagram colours seem odd. Do they show like this for you? Also you should add App Configuration in the same line as SCC-WP

I think I was facing some color issue in diagram and from newer stencils icons unable to pick the image present in boundary. Let me update this once again.

---

Update - Found the reason for this behavior, there is a setting in draw.io, to disable adaptive colors with which the appearance is same in different themes. Changed from default to None

[ocofaigh]

There doesn’t seem to be tests added for the new variations?

[ocofaigh]

Alternatively we could write a test that ensures all of the code in the new variations matches the code in the current variations. Then we wouldn't need to add more tests that provision resources. perhaps create a follow up issue for that? I don't want to hold this Pr up any longer

[ocofaigh]

@imprateeksh I have one request to push to this PR please. Can you:

1. Bump to latest git submodule git submodule update --remote --merge
2. Delete the symlink: rm -f .pre-commit-config.yaml
3. Recreate it using ln -s common-dev-assets/module-assets/.pre-commit-config.yaml .pre-commit-config.yaml
4. Run pre-commit run --all-files and fix any failing hooks

[terraform-ibm-modules-ops]

🎉 This PR is included in version 5.1.0 🎉

The release is available on:

• GitHub release
• v5.1.0

Your semantic-release bot 📦🚀