Selective provisioning of observability resources

[in-1911]

Description

In a scenario where the stack is deployed while re-using most of the resources (security services, Watson SaaS), I would like to be able to configure the stack variables to skip provisioning of some (or all) of the new observability resources by the corresponding member DA.
Because of the complexity of the resource configuration something like an override.json approach may be a better option here.

• ATracker routes and targets
• LogDNA instance
• Cloud Monitoring instances
• COS buckets for the above

New or affected modules

---

By submitting this issue, you agree to follow our Code of Conduct

[Khuzaima05]

@in-1911

Should I expose the four boolean variables— Activity Tracker routes and targets, LogDNA instance, Cloud Monitoring instances, and COS buckets—in the input and output of the core security services stack definition, and then utilize them within the stack-retrieval-augmented-generation module's stack definition?

[Khuzaima05]

As per discussion, no implementation is needed at this time. I am unassigning myself from this task as I am currently focusing on other high-priority tasks.

[Khuzaima05]

PR: #222

[Khuzaima05]

PR merged, Closing this issue