Description

let's say I have an apache process group I want to control.

• when using supervisord.running, the name must be apache:* (which is the same notation used by supervisor)
• when using supervisord.dead, the name must be apache: (without the *)

As both states mirror each other, I expect them to use the same convention for name, the one from running since it

❓ General Issue

As I'm upgrading CDK in many projects to remove EOL Node 10.x lambdas, I'm seeing an upgrade go from 10.x -> 12.x instead of the expected 14.x (current LTS). This means that I'm going to need to revisit this upgrading process sooner than if this were set to 14.x.

This construct is specifying 'nodejs12.x' https://github.com/aws/aws-cdk/blob/b1ecd3d49d7ebf97a54a80

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

Add package manager support for windoz users with chocolatey:
like here: https://github.com/bridgecrewio/yor-choco

Hello,

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

Regards

We should surface to users earlier in the pipeline workflow what the possible repo sources are (GitHub, CodeCommit, Bitbucket).

pipeline --help
pipeline init --help
at the very least, possibly pipeline update(/deploy) --help as well...

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).