docs: Add warnings against customizing deployment templates #4648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Context
Enterprise customers need to understand that customizing Quilt-provided CloudFormation templates or Terraform modules can negatively impact their service agreement coverage. These warnings provide gentle but clear guidance while offering a path forward through account manager consultation.
🤖 Generated with Claude Code
Greptile Overview
Greptile Summary
Added important warnings in the CloudFormation and Terraform deployment sections to inform enterprise customers that customizing Quilt-provided templates or modules may negatively impact service agreement coverage. The warnings are well-placed, consistent with existing documentation style, and provide a clear path forward through account manager consultation.
Confidence Score: 5/5
Important Files Changed
File Analysis
Sequence Diagram
sequenceDiagram participant User as Enterprise Customer participant Docs as Installation Documentation participant CF as CloudFormation/Terraform participant Support as Quilt Account Manager User->>Docs: Read deployment instructions Docs->>User: Display warning about template modification alt Customer needs customization User->>Support: Contact for customization options Support->>User: Provide supported customization path User->>CF: Deploy with approved customizations else Customer follows standard path User->>CF: Deploy with unmodified templates end CF->>User: Deployment complete with full service agreement coverage