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

feat: parse .terraform-version files for stacks dirs #1746

Closed
wants to merge 24 commits into from

Conversation

ansgarm
Copy link
Member

@ansgarm ansgarm commented Jul 2, 2024

Open

  • Rebase
  • Write tests
  • Register changes

dbanck and others added 24 commits June 11, 2024 12:29
The EventBus has a fixed list of topics that anyone can subscribe to.
Whenever an event is published on a topic, all subscribers are notified.
This moves all logic related to Terraform root modules into a feature.
The feature keeps track of installed providers and modules.
This moves all logic related to module files into a feature. The feature
contains all state, jobs, hooks, and decoder related files.
This moves all logic related to Terraform's variable definition
files into a feature.
All jobs are now scheduled from their respective feature. There is no
need for a separate indexer anymore.
The hooks are only relevant inside the modules feature and have been
moved into the feature.
We don't schedule any jobs when walking a workspace for the first time,
so the walker only needs to report directories and their files via
discover events.
This better reflects the new structure as the walker only walks
directories and fires events now. The state is managed in the separate
features after they get a discover event.
All parsing related logic has been moved to the specific features. All
job implementations now live in their respective features as well.
The global decoder now only acts as a "proxy" and will use a more
specific decoder from a feature depending on the language ID.
The state has been moved to separate features. The global state now
only contains entities that are relevant to everything.

The new change tracking has been partially lifted into the features and
only the generic part is kept in the global state.
We keep track of all features in this central location. This should be
the main place you need to extend whenever a new feature is introduced.
Document synchronization handlers will now fire an event for every
incoming request. Features can subscribe to these events.

Language feature handlers will now wait for running jobs for a
directory before attempting to complete the request and return data.
* Update changelog

* Update VERSION
Signed-off-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>
Signed-off-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>
@ansgarm ansgarm changed the base branch from implement_stacks to stacks_static_schema July 4, 2024 07:54
@dbanck dbanck force-pushed the stacks_static_schema branch 2 times, most recently from 2ed3e9f to 2bcbad8 Compare July 5, 2024 14:17
Base automatically changed from stacks_static_schema to pre-release July 5, 2024 14:23
@ansgarm
Copy link
Member Author

ansgarm commented Jul 8, 2024

superseded by #1756 (rebasing hell, yay)

@ansgarm ansgarm closed this Jul 8, 2024
Copy link

github-actions bot commented Aug 8, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants