imjasonh/terraform-provider-pteraform
1
0
Fork 0
mirror of https://github.com/imjasonh/terraform-provider-pteraform synced 2026-07-07 00:34:02 +00:00
Code Activity
No description
3 commits 4 branches 0 tags 97 KiB
Find a file
Exact
Jason Hall 6953c06b16
Update README.md
2023-09-30 22:11:22 -04:00
.github Initial commit 2023-09-30 21:37:52 -04:00
docs initial commit 2023-09-30 22:08:14 -04:00
examples initial commit 2023-09-30 22:08:14 -04:00
internal/provider initial commit 2023-09-30 22:08:14 -04:00
tools Initial commit 2023-09-30 21:37:52 -04:00
.gitignore Initial commit 2023-09-30 21:37:52 -04:00
.goreleaser.yml Initial commit 2023-09-30 21:37:52 -04:00
go.mod initial commit 2023-09-30 22:08:14 -04:00
go.sum Initial commit 2023-09-30 21:37:52 -04:00
LICENSE Initial commit 2023-09-30 21:37:52 -04:00
main.go initial commit 2023-09-30 22:08:14 -04:00
README.md Update README.md 2023-09-30 22:11:22 -04:00
terraform-registry-manifest.json Initial commit 2023-09-30 21:37:52 -04:00

README.md

terraform-provider-pteraform

This Terraform provider allows you to invoke terraform apply from within a Terraform resource.

Sometimes I have good ideas, and sometimes I have bad ideas, and sometimes I can't tell which is which.

Usage

provider "pteraform" {}

resource "pteraform_apply" "first" {
  working_dir = "${path.module}/first"
}

resource "pteraform_apply" "second" {
  working_dir = "${path.module}/second"
}

Applying this config will run terraform apply -auto-approve in both directories.

If you change the contents of one of those directories, only that directory will be applied again. terraform plan will show you which directories changed (not very usefully).

Do not use this in anything approaching real life.

Pteraform...?

terraform is a reserved provider name. I know right?