We have Changelog documentation here:

https://docs.saltproject.io/en/latest/topics/development/changelog.html

However, this documentation is not integrated or referenced in our documentation on how to create PRs:

https://docs.saltproject.io/en/latest/topics/development/contributing.html

The "Changelog" section appears BEFORE the Contributing section, but should likely be placed INSIDE

Using --change-set-name with multiple, parallel deployments results in context-bleed of the various changeset names being provided to each independent run of cdk deploy. I originally raised this issue on aws/aws-cdk#14316, but it was closed by @rix0rrr with instructions to use ---change-set-name. Unfortunately, the fix suggested

Requesting that you add the new Gitlab Provider as a new VCS Provider.

See here for the provider details: https://registry.terraform.io/providers/gitlabhq/gitlab/latest

See below ...

Monthly cost change for /home/atlantis/.atlantis/repos/XXX.tfplan
    Amount:  -$281 ($914 -> $633)
    Percent: --31%

Looks like a bug in this function: https://github.com/infracost/infracost/blob/master/internal/output/diff.go#L281

Hello,

Do you plan to support Terraform scans with OpenStack in the future ?

Regards

Hey,

When releasing a new version of my service using svc deploy I see that the whole process takes around 5 minutes, I suspect that due to the default deregistration_delay value, is there a friendly way to set it in the manifest so it will be set to a lower value?

Garbage collection works by listing everything with the gc-tag. In a busy cluster, we really want that filter to happen server-side and ideally using an index of some sort.

That means we should use a Kubernetes label, not an annotation.

I think this will require a two-step migration plan (write both but continue to read annotation; release; drop support for annotation; release).