refactor(config): Begin designing v1alpha2 config schema #1552
Conversation
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
The v1alpha2 schema represents the next structure of the `windsor.yaml` file. The major change involves creating a dedicated block for configuring the workstation. Now, workstations could be considered more of a common resource that does not strictly belong to a context. If a local workstation exists, contexts can provision resources on it and leverage its services. Other changes involve organizing cloud provider blocks, and simplifying Terraform backend config. Some minor changes like dropping "provider" and "id" are in preparation for a blueprint focused `values.yaml` feature in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The v1alpha2 schema represents the next structure of the
windsor.yamlfile. The major change involves creating a dedicated block for configuring the workstation. Now, workstations could be considered more of a common resource that does not strictly belong to a context. If a local workstation exists, contexts can provision resources on it and leverage its services.Other changes involve organizing cloud provider blocks, and simplifying Terraform backend config.
Some minor changes like dropping "provider" and "id" are in preparation for a blueprint focused
values.yamlfeature in the future.