Skip to content

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

Addon beta 1.2.3

09 Dec 17:55
Compare
Choose a tag to compare
Addon beta 1.2.3 Pre-release
Pre-release
v1.2.3-addon-beta

add bimcloud api key in stack config

Addon Beta 1.2.2

09 Dec 15:35
Compare
Choose a tag to compare
Addon Beta 1.2.2 Pre-release
Pre-release
v1.2.2-addon-beta

update ibm_catalog.json - variables name

v2.1.1

04 Dec 14:43
v2.1.1
404b83e
Compare
Choose a tag to compare

2.1.1 (2024-12-04)

Bug Fixes

  • added fix which was preventing some stack output from showing
  • added a fix where the value of the watsonx_admin_api_key was not being passed to the Workload - Sample RAG App Configuration member
  • added a white background to the diagram to enable it to show in dark mode (#202) (404b83e)

v2.1.0

30 Nov 12:39
v2.1.0
bf00009
Compare
Choose a tag to compare

2.1.0 (2024-11-30)

Updates (#224) (bf00009)

  • Fixed bug in Security Compliance Center DA which can produce error on Event Notifications integration (more info)

  • When upgrading DAs that support creating a KMS key, you may see the update force_delete = true -> false identified when upgrading. This is expected since the feature has been deprecated by the service. There is no impact to every day operations.

  • Several DAs have been updated to now scope the KMS authorisation policy to the exact KMS key. During upgrade, you will see a destroy and recreate of these policies, however the new poliocy is created before the old one is, so there is no disruption to every day operations.

  • The Event Notifications COS integration has been updated to communicate with the bucket using the direct endpoint instead of public endpoint as before. This is done as an update in place, and has no impact on every day operations.

  • deps: Update stack definition member versions:

    Stack Change
    Account Infrastructure Base v1.12.11 --> v1.16.0
    Essential Security - Encryption Key Management v4.15.13 --> v4.17.0
    Essential Security - Event Notifications v1.10.19 --> v1.15.0
    Essential Security - Secrets Manager v1.18.6 --> v1.19.0
    Essential Security - Security Compliance Center v1.20.2 --> v1.24.1
    Gen AI - Databases for Elasticsearch v1.20.4 --> v1.23.5
    Workload - Code Engine Projects v2.0.1 --> v2.1.1

addon beta 1.2.1

29 Nov 16:04
1457ef6
Compare
Choose a tag to compare
addon beta 1.2.1 Pre-release
Pre-release
v1.2.1-addon-beta

update ibm_catalog.json: change install_type from fullstack to extension

Addon beta 1.2.0

29 Nov 15:59
Compare
Choose a tag to compare
Addon beta 1.2.0 Pre-release
Pre-release
v1.2.0-addon-beta

update configuration: delete type, desc, default value

v2.0.1

17 Oct 10:27
v2.0.1
b1ff75f
Compare
Choose a tag to compare

2.0.1 (2024-10-17)

Bug Fixes

  • docs: change prefix description, add permission to roks catalog flavor (#216) (69f2b41)
  • updated the version of Observability DA to pull in a fix for Cloud Logs where instance provisioning can fail due to the COS authorisation policy not being created in time.
  • updated the version of the Sample App DA to pull in fix for race condition with ingress and CI pipeline
  • updated the CI, CD, and CC pipeline property values to address some gaps (#208) (b1ff75f)

v2.0.0

01 Oct 15:46
v2.0.0
e302b82
Compare
Choose a tag to compare

2.0.0 (2024-10-01)

Features

BREAKING CHANGES

  • No upgrade supported from 1.x

v1.0.1-addon

12 Sep 10:11
Compare
Choose a tag to compare
v1.0.1-addon Pre-release
Pre-release
dev-addon-poc-v1.0.1

feat: addon poc content

v1.2.0

04 Jul 17:34
v1.2.0
07f7f3e
Compare
Choose a tag to compare

Retrieval Augmented Generation Pattern Stack v1.2.0 Release Notes

This release includes several updates to the underlying members of the Retrieval Augmented Generation Pattern stack.

Observability

Features

  • Monitoring for all buckets created by the solution can now be configured by setting cloud_monitoring_provision to true.
  • Provisioning of logging or monitoring instances can now be opted out of using new boolean input variables log_analysis_provision and cloud_monitoring_provision.
  • Existing cloud monitoring instances can now be used with the new input variable existing_cloud_monitoring_crn.
  • New variables enable_at_event_routing_to_cos_bucket and enable_at_event_routing_to_log_analysis provide ability to route Activity Tracker either to a COS bucket, or an existing Log Analysis instance (or both).

Bug Fixes

  • Default value for region in instances Deployable Architecture is updated.

WatsonX SaaS Services

Features

  • Catalog tile has been updated and Deployable Architecture has been renamed to "Watsonx.ai SaaS with Assistant and Governance".
  • Support has been added for provisioning watsonx.data.
  • Some Watson services can now be deployed in the jp-tok region.

Bug Fixes

  • Error fixed when requesting no Watson project to be created.
  • Storage delegation now works when KMS is private.
  • Reference architecture diagram updated for accuracy.

Security Service - Security Compliance Center

Features

  • Event Notifications destinations, topics, and subscriptions can now be created for the SCC instance.
  • SCC attachments can now be created using the profile_attachments input variable.
  • SCC Cloud Object Storage (COS)-related outputs have been added.

Bug Fixes

  • Variable descriptions have been cleaned up.
  • Bug fixed in agents Deployable Architecture where Kubernetes provider config had a typo.

Security Service - Secret Manager

Features

  • Support has been added for use cases where KMS is in a different account using the new optional variable ibmcloud_kms_api_key.
  • Event Notifications destinations, topics, and subscriptions can now be created.

Bug Fixes

  • Improved the accuracy and details of the description of the input and output variables for the Deployable Architecture.

Sample RAG App Configuration

Bug Fixes

  • Watson Assistant code updated to allow for destruction of resources.
  • Watson Discovery API URL prefixed with https.

Important Notes

  • Upgrading from an older version may result in some destroys due to the major version update of the COS module. This is expected and should not be disruptive to everyday operations.
  • When upgrading to this version, you may end up with a duplicate Assistant within your Watson Assistant instance. We recommend deleting the original Assistant from the Watson Assistant instance after the upgrade.