Skip to content

Conversation

@jubrad
Copy link
Contributor

@jubrad jubrad commented Nov 19, 2025

Motivation

Revival of Jun's Pr to shift the cloud specific terraform install and upgrade structure +docs for the new terraform.

@jubrad jubrad requested review from SangJunBak and kay-kim November 19, 2025 19:43
@jubrad jubrad requested a review from a team as a code owner November 19, 2025 19:43
@SangJunBak
Copy link
Contributor

@jubrad thanks for reviving this!

Copy link
Contributor

@kay-kim kay-kim left a comment

Choose a reason for hiding this comment

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

Hey ... won't have time to add a patch to this today (double-checking the upgrade)... so, am leaving some comments for now in case people have a window free.
Depending on when, I'll continue reviewing or patching. Heads up ... I'm out starting Monday next week.

{{</ tip >}}
| Guide | Description |
|-------|-------------|
| [Terraform Provider](/installation/install-on-aws/terraform-module/) | Install Materialize on AWS using our new Unified Terraform Provider |
Copy link
Contributor

Choose a reason for hiding this comment

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

In the Description for the new Unified .... Do we want to add Recommended annotation? like
| Recommended. Install Materialize ...

| Guide | Description |
|-------|-------------|
| [Terraform Provider](/installation/install-on-aws/terraform-module/) | Install Materialize on AWS using our new Unified Terraform Provider |
| [Terraform Provider (legacy)](/installation/install-on-aws/legacy-terraform-module/) | Install Materialize on AWS using our Terraform Provider (legacy) |
Copy link
Contributor

Choose a reason for hiding this comment

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

The description "using our Terraform..." -> "using our legacy Terraform Provider"


```hcl
name_prefix = "simple-demo"
aws_region = "us-east-1"
Copy link
Contributor

Choose a reason for hiding this comment

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

should we mention as a comment that they can change the aws_region?

@@ -0,0 +1,187 @@
---
title: "Upgrade Overview"
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh yeah, I did just notice that, and I'm not sure I agree.
I knid of want the landing page portion to go away and think we should move back to an upgrade overview doc 😆

Probably best to chat through this through on zoom.

Copy link
Contributor

@kay-kim kay-kim Nov 20, 2025

Choose a reason for hiding this comment

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

It's only because of the current organization that it's included at the top. That is, for the upgrade landing page, we would want to reorg the other files.
Currently, as it stands, we have:

  • Self-Managed Deployments
    • Install on kind
      • Upgrade
    • Install on AWS
      • TF
      • TF Legacy
        • Install
        • Upgrade
        • Req Config
    • Install on Azure
      • TF
      • TF Legacy
        • Install
        • Upgrade
        • Req Config
    • ...
    • Upgrading

So ... we might want to go:

  • Self-Managed Deployments
    • Install
      • Install on kind
      • Install on AWS
      • ...
    • Upgrade <-- This can be the separate landing page overview.
      • Upgrade on kind
      • Upgrade on AWS
      • ...

@jubrad jubrad changed the title docs: Relabel GCP guides as legacy Terraform guides add new terraform docs Nov 20, 2025
@jubrad jubrad force-pushed the jubrad/new-terraform-docs-2 branch from c1937ea to c3bf896 Compare December 2, 2025 20:33
- Moves the install, upgrade, and configuration docs into a subdirectory called Terraform Provider (Legacy)
- Creates aliases for each of the moved pages
- `Installation > Install on GCP `-> `Installation > Install on GCP > Terraform Provider (Legacy) > Install`
- Removed terraform references from the Deployment guideline appendix and pushed them into the Configuration appendix
- Changed from "Required configuration" to just "configuration"

docs: Relabel AWS guides as legacy Terraform guides

- Does the same work as the GCP commit

docs: Relabel Azure guides as legacy Terraform guides

- Does the same thing as the GCP commit
- Removes terraform configuation values given they weren't rendered. e.g. enable_disk_support

Update doc links

Add docs for new terraform modules.
@jubrad jubrad force-pushed the jubrad/new-terraform-docs-2 branch 3 times, most recently from 4ce9781 to 09c8029 Compare December 3, 2025 01:34
@jubrad jubrad force-pushed the jubrad/new-terraform-docs-2 branch from 09c8029 to 718192a Compare December 3, 2025 15:21
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