Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terraform Stacks Editor Support #1699

Open
7 tasks
jpogran opened this issue Feb 26, 2024 · 0 comments
Open
7 tasks

Terraform Stacks Editor Support #1699

jpogran opened this issue Feb 26, 2024 · 0 comments
Labels
enhancement New feature or request meta

Comments

@jpogran
Copy link
Contributor

jpogran commented Feb 26, 2024

Problem Statement

Terraform Stacks is a new way of organizing Terraform infrastructure-as-code configurations. A Terraform stack represents a graph of interconnected components that are managed across many independent deployments.

The authoring stage will be one of the primary interface points for Terraform Stacks users. Having and editor provide support for Terraform Stacks files would ease the use of Stacks for new users and enable advanced users with more complex configurations.

Proposal

In the initial preview a user will author Terraform Stack configurations and initiate a deployment by merging code to a GitHub repository that is linked with Terraform Cloud. When the merge happens TFC plans and applies the stack according to the deployment file.

The intellisense, inline documentation, syntax validation and other advanced language features of the Terraform Extension for VS Code will provide a guided introduction to using Stacks as well as powerful introspection through deep reference parsing for advanced users.

Support will be delivered in a phased manner:

Phase 1: Basic Language Support

  • Claim new language identifiers and file extensions
  • Syntax highlighting support for new keywords
  • Add new schema to terraform-schema
  • Add support for completion, hover and semantic tokens of new language keywords and existing provider schema

Phase 2: Complex Language Support

  • Add complex support for completion, hover and semantic tokens of new language keywords and existing provider schema
  • Reference target and origin resolution
  • Inputs and outputs completion between stacks, components and deployments

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@jpogran jpogran added the enhancement New feature or request label Feb 26, 2024
@dbanck dbanck added the meta label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request meta
Projects
None yet
Development

No branches or pull requests

2 participants