infrastructure-as-code
Here are 1,302 public repositories matching this topic...
Describe the solution you'd like
It would be nice to have a way to control whether a VM starts on boot or not. Maybe a new autostart option to salt.states.virt.running and/or salt.states.virt.defined? Or maybe a new function?
Describe alternatives you've considered
I'll probably use salt.modules.virt.set_autostart for now.
-
Updated
Nov 23, 2021 - Go
Description
GoReleaser displays the following warning.
$ goreleaser release --rm-dist
• releasing...
• loading config file file=goreleaser.yml
...(snip)...
• docker images
• DEPRECATED: `docker.use_buildx` should not be used anymore, check https://goreleaser.com/deprecations#dockerusebuildx for more info
• DEPRECATED: `docker.use_buildx` should n
What is the problem?
Looks like the SqlServerEngineVersion.VER_14_00_3192_2_V1 is no longer supported?
I discovered this while trying to run the s3-instance integration test.
To get passed the problem in our pipeline I switched the test to use SqlServerEngineVersion.VER_14, but we
-
Updated
Nov 22, 2021 - Java
-
Updated
Nov 22, 2021 - Go
-
Updated
Nov 13, 2021 - Go
See infracost/infracost#1135 and the follow-up comment for what's needed
-
Updated
Nov 22, 2021 - Go
Hello Team,
Here is the my current checkov_scan.yml file
name: Run Checkov action serverless
id: checkov1
uses: bridgecrewio/checkov-action@master
with:
#skip_check: CKV_AWS_23 # optional: skip a specific check_id
#quiet: true # optional: display only failed checks
#log_level: DEBUG # optional: set log level. Default WARNING
- terrascan version: 1.9.0
- terraform version: 1.0.1
Enhancement Request
Other security scanning tools (e.g. checkov and tfsec) have a --soft-fail flag or equivalent option that allows you to always exit with 0 status.
Extremely useful when running the tool without halting a pipeline for example.
I currently use a workaround, but something more concrete would be very desira
-
Updated
Nov 22, 2021
-
Updated
Nov 19, 2021 - Python
-
Updated
Nov 20, 2021 - Go
-
Updated
Nov 18, 2021 - Python
-
Updated
May 16, 2021
-
Updated
Nov 17, 2021 - JavaScript
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
We all have an aws_api_gateway_account resource inside each region of AWS that will by default output as unmanaged. We s
-
Updated
Nov 5, 2021 - Go
-
Updated
Sep 21, 2021 - JavaScript
-
Updated
Oct 14, 2021 - HCL
-
Updated
Sep 30, 2020 - Go
-
Updated
May 8, 2021 - Markdown
-
Updated
Nov 18, 2021 - Ruby
-
Updated
Nov 22, 2021 - Open Policy Agent
-
Updated
Oct 5, 2021 - Go
-
Updated
Nov 17, 2021 - Go
-
Updated
Feb 27, 2018 - HCL
Improve this page
Add a description, image, and links to the infrastructure-as-code topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the infrastructure-as-code topic, visit your repo's landing page and select "manage topics."

