Narthana Epa

Hmm, so it looks like if you create a stack with the default value for the `BuildkiteAgentScalerVersion` parameter and then upgrade to a stack that has a new default value...

So I've had a bit of trouble trying to reproduce this issue. And we've definitely upgraded stacks internally where `BuildkiteAgentScalerVersion` was not set. Turns out, it's a known issue when...

> I think we can make the default value "" and then use a conditional to detect if the value has been explicitly set Hmm, looks like my [attempt](https://github.com/buildkite/elastic-ci-stack-for-aws/commit/9c2c8df67c927e3dd238e81c05770be31703327f) to...

Hi @mf-lit. Thanks for making this PR. Unfortunately, we think it's not likely to work as expected. So the way the instances in the elastic stack are terminated is not...

Cool, https://github.com/jdxcode/rtx/pull/253 mainly covers this use case now. It would be nice if we didn't have to resort to environment variables, but this is good enough until it lands in...

I guess there are two opinions I have: 1. Tools should follow the XDG Spec 2. Tools should store their config in their own directories Let's ignore 1. for the...

Hi @simonbyrne thanks for raising this. We've had a bit of a guess of what your use case for this is, but please let us know if we're off track....

Thanks for getting back to us about the usability of the `redact-vars` feature @goodspark. I suppose catching things like this is part and parcel of being cautious and using a...

Sorry, we didn't respond earlier @goodspark, but we've taken another look at this. How about if we add a flag that allows skipping warnings for the variables that are too...

Thanks for raising this @ChrisBr, I think it makes more sense to have `agent redacted-vars add` instead. Implementing this feature will require some delicate changes to how the redactor works,...