version 3: initial implementation #22
Merged
Conversation
This file contains 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
gopls does not work when only specifying the major and minor version anymore with go 1.22
This commit introduces the initial version 2 of the dependencies-tool. Major changes: - The application dependencies are now defined in a single YAML file per app, instead of multiple TOML files. YAML anchors can be used to reduce duplication. - The dependencies for multiple distributions can be defined in the same YAML file. - Dependencies can either be soft or hard. Hard dependencies enforce a strict order but can not contain loops, ensuring that dependent services are ordered before. Soft dependencies do not enforce an order but allow loops. - The dependency on having a .baur.toml file is removed. All configuration files in a directory tree are discovered. The name or path suffix of the configuration files that are discovered can be configured, also directories matching certain names can be excluded from the discovery. - The ENVIRONMENT and REGION command line arguments are replaced with a single DISTRIBUTION argument. - The export sub command now exports the dependencies of all distributions into a single file, instead of only for the specified ENVIRONMENT and REGION. - The deploy-order sub command is renamed to order.
|
back to draft, resolving dependencies does not work correctly when |
fho
changed the title
fho
added a commit
that referenced
this pull request
Feb 16, 2024
This commit introduces the initial version 3 of the dependencies-tool. Major changes: - The application dependencies are now defined in a single YAML file per app, instead of multiple TOML files. YAML anchors can be used to reduce duplication. - The dependencies for multiple distributions can be defined in the same YAML file. - Dependencies can either be soft or hard. Hard dependencies enforce a strict order but can not contain loops, ensuring that dependent services are ordered before. Soft dependencies do not enforce an order but allow loops. - The dependency on having a .baur.toml file is removed. All configuration files in a directory tree are discovered. The name or path suffix of the configuration files that are discovered can be configured, also directories matching certain names can be excluded from the discovery. - The ENVIRONMENT and REGION command line arguments are replaced with a single DISTRIBUTION argument. - The export sub command now exports the dependencies of all distributions into a single file, instead of only for the specified ENVIRONMENT and REGION. - The deploy-order sub command is renamed to order.
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.
This commit introduces the initial version 3 of the dependencies-tool.
Major changes:
app, instead of multiple TOML files. YAML anchors can be used to
reduce duplication.
YAML file.
strict order but can not contain loops, ensuring that dependent
services are ordered before.
Soft dependencies do not enforce an order but allow loops.
All configuration files in a directory tree are discovered.
The name or path suffix of the configuration files that are discovered
can be configured, also directories matching certain names can be
excluded from the discovery.
single DISTRIBUTION argument.
distributions into a single file, instead of only for the specified
ENVIRONMENT and REGION.