This fixes the issue around variables not working for custom commands on 0.12.54: https://github.com/garden-io/garden/pull/4114 See context in the commit message. We need to release this as a patch on top of 0.12.54 which is basically broken as is.

Would anyone be available to cut a release for this fix? (cc @big-spring-14945 or @curved-intern-91221 🙏)

Sure, should we cut it off today?

here is a beautiful example of a release message ❤️ https://discord.com/channels/817392104711651328/1089798457478365244/1098973611517296651

@swift-garage-61180 How do we do base helm charts with actions now?

We essentially just merge in the child module's values, and use the parent module's chart path: https://github.com/garden-io/garden/blob/0.13/core/src/plugins/kubernetes/helm/handlers.ts#L231-L234

but how can the user accomplish this without using modules?

That's how we convert

helm

modules referencing base charts. For new

helm

Deploys, just point to the chart path you want to use and provide the values.

Currently the chart path schema only allows subpaths though

Gotcha. I think we should loosen that restriction—I don't see any problems with that.

What ya'll think about disabling replies in this channel to avoid chains like above? Then it's either a single message or a thread.

I have some open questions on the

terraform

plugin and the terminology we use in it for

0.13

https://github.com/garden-io/garden/pull/4130

I need help with making pulumi related provider / module fields mutually exclusive. Could someone point me on how to achieve it?

Here's a quick one: https://github.com/garden-io/garden/pull/4137 Looks like we forgot to look at the

check-docs

step when we merged the

community

command.

@curved-intern-91221 @ancient-diamond-80011 I'm back now, sorry for moving the session around.

Here is the fix for

deploy --sync

command: https://github.com/garden-io/garden/pull/4139

Hey all Just merged that follow-up logger PR. It fixes some issues with the first iteration but there's always a chance some other log lines look off. Please flag if you notice anything silly, such as badly placed durations, missing colors, etc. The notable difference is that in most cases you don't need to add extra config to log entries. E.g., now you can just do

log.warn("oh noes")

as opposed to

log.warn({ msg: chalk.yellow("oh noes"), symbol: "warning})

. So it's more opinionated in a way, but that could also break some existing lines. If we realise we need more control we can always re-introduce it, but it feels right to start conservatively. https://github.com/garden-io/garden/pull/4138

Could you assign/include @quaint-dress-831 and @bright-policeman-43626 to any docs-related PRs that are live or TODO, @calm-family-29323 @curved-intern-91221? Community Engineering will be having a look through the docs and deciding if anything needs further elaboration or explaining, so we should include them in any in-flight discussions.

When I hit CTRL-C in

garden dev

, I get this error:

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
    at Dev (/Users/ths/src/garden/core/build/src/commands/dev.js:100:22)
    at App (/Users/ths/src/garden/node_modules/ink/build/components/App.js:42:9)
^C%

  The

dev

command has logic that's intended to catch CTL-C / SIGINT, but it doesn't seem to be working right. CC @alert-helicopter-61082

Hey, there was a small regression recently with

.only

added to some tests suite on the 0.13-branch. Fix is here: https://github.com/garden-io/garden/pull/4147

I notice that the logs command is broken on 0.13 (haven't tested on 0.12) and no longer respects the

--since

and

--tail

flags. Instead it just prints all the logs. I also added this to the internal "empathy" doc.

@alert-helicopter-61082 Currently it seems that the task status is resolved even if

force == true

which seems unnecessary I think it'd make sense to just execute the actions and not even bother resolving the statuses

Anyone want to review+test this? https://github.com/garden-io/garden/pull/4151

I'm doing a bit of house cleaning, had some half-baked branches open before the vacation 😛

https://github.com/garden-io/garden/pull/4150 Could someone pick up the TODOs here?

We're including a

.git

folder inside the

static

folder in our release assets. Is that by design?

https://github.com/garden-io/garden/pull/4156 seems there are a few failing CI tests on

main

. @ancient-diamond-80011 would you mind taking a look? Might be some fixes on

0.13

that need cherry-picking over at least.

Can we have someone take a look at https://discord.com/channels/817392104711651328/1103003569654865941 ? This user is asking for a Garden release that uses a more recent Node

https://github.com/garden-io/garden/pull/4161 should fix the above summary: we already have installed the newer auth plugin, but unlike

kubectl

, the

helm

cli does not use it by default unless you set an env var specifically (and they consider that not-a-bug in upstream)

Looks like something slipped through here: https://app.circleci.com/pipelines/github/garden-io/garden/16794/workflows/c4e27d6c-cbb4-45b0-b8c5-e8f01eec026e/jobs/286185