feat:exposing CBRs in DA

[Aditya-ranjan-16]

Description

Exposed CBRs in DA

GIT Issue

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Exposes CBRs in DA

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.

[Aditya-ranjan-16]

/run pipeline

[ocofaigh]

Don't forget when adding a new input variable to a DA, it needs to go into ibm_catalog.json too so it can be ordered.

Also this PR is missing supporting markdown doc which the variable descrption needs to point to. We already have one in this repo here, so you should update that

[Aditya-ranjan-16]

/run pipeline

[Aditya-ranjan-16]

/run pipeline

[Aditya-ranjan-16]

/run pipeline

[Aditya-ranjan-16]

/run pipeline

[Ak-sky]

Left few comments.

[Ak-sky]

@Aditya-ranjan-16, also please link the GIT issue in this PR description.

[Aditya-ranjan-16]

/run pipeline

[Aditya-ranjan-16]

/run pipeline