search

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

A deployable architecture that automates the deployment of a sample gen AI Pattern on IBM Cloud, including all underlying IBM Cloud and WatsonX infrastructure.
Apache License 2.0
1 stars 11 forks source link

Enable skipping SCC provisioning #131

Closed in-1911 closed 2 months ago

in-1911 commented 5 months ago

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 a new SCC instance. At some point I might still want to be able to create some attachments, but currently the SCC DA does not have much fine-grained control over that.

At the moment, I would have to just not deploy the SCC DA if I do not want to create a new SCC instance. Another option is to just delete that member DA from the stack instance in the project. Neither option would work if we will be creating SCC attachments through the stack while re-using the instance.

This feature would probably require a change in the SCC DA as well (to enable using an existing instance) or a change in stack framework that allows to override the stack member with pre-defined output values - to keep any wiring within the stack intact.

New or affected modules

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

ocofaigh commented 4 months ago

@in-1911 In https://github.com/terraform-ibm-modules/terraform-ibm-scc-da/issues/140 we are adding the ability to pass an existing SCC instance to the SCC DA. That will at least cover the use case of being able to create attachements in an existing instance.