infrastructure-as-code
Here are 872 public repositories matching this topic...
Description
I get the following warnings once a minute:
2020-06-23 23:11:13,900 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt/master/roots/mtime_map: /srv/salt/a/b/c/ifcfg-eth0:0:1533517049.0
2020-06-23 23:11:13,901 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt
-
Updated
Sep 29, 2020 - Go
-
Updated
Sep 30, 2020 - Java
[cdk-pipelines] Stacks in stage doesn't get deployed in parallel when stage.add_application is used?
❓ Parallel Deployment to Multiple Accounts
-
Updated
Sep 29, 2020 - Go
- Dockerfile include terraformer version with all providers
- Script install providers on start container
- Manual in README about docker run command, include volume mounts for outputs, credentials and etc.
-
Updated
Sep 3, 2020 - Python
-
Updated
Sep 14, 2020 - Python
-
Updated
Sep 28, 2020
-
Updated
Sep 16, 2020
-
Updated
Sep 29, 2020 - JavaScript
-
Updated
Sep 30, 2020 - Go
When I run infracost --help, I see the following and it's not clear from the description which one I should use:
--tfjson value Path to Terraform Plan JSON file
--tfplan value Path to Terraform Plan file. Requires 'tfdir' to be set
--tfdir value Path to the Terraform project directory (default: current working directory)
One user has alre
-
Updated
Sep 17, 2020 - Go
-
Updated
Sep 28, 2020 - Ruby
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
copilotfrom/infrastructure/ - Each manifest has an
imageproperty that points to
-
Updated
Sep 23, 2020 - HCL
-
Updated
Feb 27, 2018 - HCL
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).
-
Updated
Sep 23, 2020 - HCL
-
Updated
Sep 30, 2020 - Go
-
Updated
Sep 15, 2020 - Shell
-
Updated
Sep 29, 2020 - Python
Because having to type the whole commands is a pain!
-
Updated
Sep 30, 2020 - C
-
Updated
Sep 18, 2020 - Go
Found a bug in Collectors (#50). All collectors redundantly copied a bug where the Promise was not awaited.
Bug is fixed, but we should make a generic SinkCollector for all types that implement Sink<T>.
-
Updated
Sep 29, 2020 - Go
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."
I'm trying to use nbering/terraform-provider-ansible by placing it in
~/.terraform.d/plugins/linux_amd64/terraform-provider-ansible, butterraform initnever seems to actually find it (NB this works fine in 0.12.x). Why is that?Can 0.13 actually load plugins from local file-system directories (as [described in the documentation](