diff --git a/aws/README.md b/aws/README.md index 077af4e3..a9eff34e 100644 --- a/aws/README.md +++ b/aws/README.md @@ -2,8 +2,9 @@ This repository provides a set of reusable, **self-contained Terraform modules** to deploy Materialize on the AWS cloud platform. You can use these modules individually or combine them to create your own custom infrastructure stack. -> **Note** -> These modules are intended for demonstration and prototyping purposes. If you're planning to use them in production, fork the repo and pin to a specific commit or tag to avoid breaking changes in future versions. +-> **Note** +-> We recommend pinning your module sources to specific tags to avoid unexpected breaking changes in future versions. +-> We recommend updating your module source tags when updating Materialize versions, taking care to follow any instructions in the release notes. --- diff --git a/azure/README.md b/azure/README.md index 5dcfcb68..69989baa 100644 --- a/azure/README.md +++ b/azure/README.md @@ -2,8 +2,9 @@ This repository provides a set of reusable, **self-contained Terraform modules** to deploy Materialize on the Microsoft Azure cloud platform. You can use these modules individually or combine them to create your own custom infrastructure stack. -> **Note** -> These modules are intended for demonstration and prototyping purposes. If you're planning to use them in production, fork the repo and pin to a specific commit or tag to avoid breaking changes in future versions. +-> **Note** +-> We recommend pinning your module sources to specific tags to avoid unexpected breaking changes in future versions. +-> We recommend updating your module source tags when updating Materialize versions, taking care to follow any instructions in the release notes. --- diff --git a/gcp/README.md b/gcp/README.md index 3e0b5cc3..02b866c8 100644 --- a/gcp/README.md +++ b/gcp/README.md @@ -2,8 +2,9 @@ This repository provides a set of reusable, **self-contained Terraform modules** to deploy Materialize on the Google Cloud Platform. You can use these modules individually or combine them to create your own custom infrastructure stack. -> **Note** -> These modules are intended for demonstration and prototyping purposes. If you're planning to use them in production, fork the repo and pin to a specific commit or tag to avoid breaking changes in future versions. +-> **Note** +-> We recommend pinning your module sources to specific tags to avoid unexpected breaking changes in future versions. +-> We recommend updating your module source tags when updating Materialize versions, taking care to follow any instructions in the release notes. ---