infrastructure-as-code

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

Currently, Trivy traverses all paths and looks for all Gemfile.lock in a container image. However, the image sometimes has only Gemfile.lock and doesn't install gems listed in the Gemfile.lock. I think a gem should have *.gemspec file if it is installed. e.g. rake.gemspec has the information about rake.

To avoid false positives from Gemfile.lock, we are probably able to take advantage of `*

When trying to deploy a stack that does not exist (for example, cdk deploy thisstackdoesnotexist), the CDK simply gives no output, even the return code is 0. This is confusing, especially for people new to the CDK.

Use Case

Use case is people not getting tripped up by this and scratching their heads, especially for people new to the CDK.

Proposed Solution

Exit with return c

Running infracost breakdown --config-file infracost.yml --terraform-workspace=ali-test correctly shows:

Error: --config-file flag cannot be used with the following flags: --path, --terraform-*, --usage-file

Our help text mentions the same thing:
      --config-file string            Path to Infracost config file. Cannot be used with path, terraform* or usage-file flags

However,

Hello,

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

Regards

Copilot doesn't seem to have correct error behavior when I try to create a Scheduled Job with the same name as an existing service.

For example, in my app right now I have the following:

❯ copilot svc ls
Name                Type
----                ----
fe                  Load Balanced Web Service

I can see this in SSM:

❯ aws ssm get-parameter --name /copilot/applicatio

Description
To complete #554, it can make sense to add resource source details for missing resources

Example
Follow pull-request attached to issues #874 #875 #876 for examples of implementation

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