Release v0.12.0 alpha.1 #1917
Closed
Release v0.12.0 alpha.1 #1917
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
This greatly expands the power of our template strings. I'll copy the
added docs here for details:
### Nested lookups and maps
In addition to dot-notation for key lookups, we also support bracketed
lookups, e.g. `${some["key"]}` and `${some-array[0]}`.
This style offer nested template resolution, which is quite powerful,
because you can use the output of one expression to choose a key in a
parent expression.
For example, you can declare a mapping variable for your project, and
look up values by another variable such as the current environment name.
To illustrate, here's an excerpt from a project config with a mapping
variable:
```yaml
kind: Project
...
variables:
- replicas:
dev: 1
prod: 3
...
```
And here that variable is used in a module:
```yaml
kind: Module
type: container
...
services:
replicas: ${var.replicas["${environment.name}"]}
...
```
When the nested expression is a simple key lookup like above, you can
also just use the nested key directly, e.g.
`${var.replicas[environment.name]}`.
You can even use one variable to index another variable, e.g.
`${var.a[var.b]}`.
This had been bothering me for ages. We now show the available keys when a key is not found.
Added some debug/silly-level log statements around auth token logic and `BufferedEventStream`.
We now wait for `BufferedEventStream` to finish flushing any buffered events and log entries before exiting a command.
This allows projects to define an arbitrary script to run on init. This is handy for running arbitrary script when initializing. For example, another provider might declare a dependency on this provider, to ensure this script runs before resolving that provider.
We now include the log level of streamed log entries sent from `BufferedEventSream`.
When running without socat we can't wait for socat to start. I'm not sure how this passed the garden-io CI, it also magically passed ours when we merged the update to the cli. This is to quickly unbreak the master branch, I'll investigate further
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.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: