Skip to content

Add forward compatibility disclaimer to README#50

Merged
bobbyiliev merged 1 commit intomainfrom
add-forward-compatibility-warning
Mar 24, 2025
Merged

Add forward compatibility disclaimer to README#50
bobbyiliev merged 1 commit intomainfrom
add-forward-compatibility-warning

Conversation

@bobbyiliev
Copy link
Copy Markdown
Collaborator

Similar to what we have in the official docs, adding a small compatibility disclaimer.

@bobbyiliev bobbyiliev merged commit a3457cd into main Mar 24, 2025
2 checks passed
@bobbyiliev bobbyiliev deleted the add-forward-compatibility-warning branch March 24, 2025 11:24
Comment thread README.md
- Materialize Helm Operator Terraform Module v0.1.8

> [!WARNING]
> This module is provided on a best-effort basis and Materialize cannot offer support for it.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might nix this, I think we would support people trying to use it to a degree, like if the TF provider clearly had bugs

Comment thread README.md
>
> It is not guaranteed to be forward-compatible and may include breaking changes in future versions.
>
> The module is intended for demonstration and evaluation purposes only, not for production use.
Copy link
Copy Markdown

@pH14 pH14 Mar 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd start with this disclaimer, and then segue into the above. I think we're also saying it has two different purposes here (evaluation only) and later (use as starting point for prod infra), and as a reader I'm not quite sure what the actual intent is

maybe something like this?

"This module is intended to be used for demonstrations, simple evaluations, and as a template for building your own production deployment of Materialize on AWS.

This module should not be relied upon for production deployments directly: future releases of those module will contain breaking changes. When used as a starting point for a production deployment, you must either fork this repo and pin to a specific version, or use the code as a reference when developing your own deployment."

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @kay-kim same feedback for the disclaimer we have in the docs as well. I'm finding our current messaging reads a little confused. Seth had a nice clear take in https://materializeinc.slack.com/archives/C085QFLB072/p1740503361409879?thread_ts=1740502884.282719&cid=C085QFLB072 that I think is a good reference

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants