OpenSpec: Standardize Terraform resource naming#29
Open
Conversation
This proposal addresses issue #28 by introducing: - Two naming variables: deployment_name (required) and environment - Consistent naming format: {deployment}-{resource-type}-{environment} - Kebab-case standardization across all resources (including IAM) - Standard tags: Name, Environment, Project, ManagedBy, Repository Includes TDD-focused spec with 17 testable scenarios and 56 implementation tasks. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add deployment_name and environment variables with validation
- Add repository variable for traceability tagging
- Add common_tags locals block for consistent AWS resource tagging
- Update all resource names to format: {deployment}-{resource-type}-{environment}
- Update CloudWatch metric filter patterns to reference new role names
- Add monitoring section to config.yaml (fixes budget.tf validation error)
- Update CI/CD workflows to pass deployment_name and environment variables
- Update example configs with monitoring section
- Remove obsolete eip.tag_name configuration
This enables multiple deployments in the same AWS account with unique,
queryable resource names and consistent tagging.
Closes #28
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Mark completed tasks for: - Variables and locals setup (1.x) - Resource naming updates (2.x-6.x) - Configuration updates (7.2, 7.3) - CI/CD updates (8.x) Note: Route53 records don't support tags (AWS limitation) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Changes
New files in
openspec/changes/standardize-resource-naming/:proposal.md- Problem statement, breaking changes, impact analysisdesign.md- Technical decisions and rationale for naming schemespecs/infrastructure/spec.md- 4 requirements with 17 testable TDD scenariostasks.md- 56 implementation tasks across 11 sectionsKey Decisions
deployment_name(required) +environment{deployment}-{resource-type}-{environment}Test plan
openspec validate standardize-resource-naming --strict- passedCloses #28
🤖 Generated with Claude Code