Terraform Version

Terraform v0.12.28
+ provider.google v3.28.0

Terraform Configuration Files

# ./main.tf
module "project" {
  source          = "../../../../blueprints/gcp/project"
  billing_account = "002A75-ABB3C9-680D62"
  folder_id       = "746484843613"
  project_id      = "di-test-mod-gcp-project-1"
  owner           = "[email protected]"

  

Description
The documentation for Installing Salt for development feels like it's out of date https://docs.saltstack.com/en/latest/topics/development/hacking.html . One example is that it seems to indicate that Python2 should be used:
On Arch Linux, where Python 3 is the default installation of Python, use the virtualenv2 command instead of virtualenv.

add support for feature launch: https://aws.amazon.com/about-aws/whats-new/2020/11/aws-lambda-now-supports-batch-windows-of-up-to-5-minutes-for-functions/

• customer can define batching window up to 300 seconds
• if batching window is defined batch size can be up to 10000
• if batching window is not defined batch size can be up to 10

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

Describe the bug
This resource causes the error WARNING: skipped AWS017 check due to error(s): value is null

And it happens even if I try to explicit skip AWS017 from cli:

tfsec --exclude AWS017
WARNING: skipped AWS017 check due to error(s): value is null

tfs

Pricing details: https://aws.amazon.com/ecr/pricing/
Terraform resources: aws_ecr_*

Hi, I just created a new environment (test2) for my app, and now I’m trying to deploy a service to that environment but it fails.

Just for context, I’m attempting to use a monorepo setup:

• My apps (services) are in /apps/
• My copilot manifests etc are in /infrastructure/copilot/
• I always run copilot from /infrastructure/
• Each manifest has an image property that points to

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

Because having to type the whole commands is a pain!