https://github.com/imjasonh/terraform-provider-pteraform

https://github.com/imjasonh/terraform-provider-pteraform

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/imjasonh/terraform-provider-pteraform
• Owner: imjasonh
• License: mpl-2.0
• Created: 2023-10-01T01:37:49.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-12-15T05:06:03.000Z (about 1 year ago)
• Last Synced: 2024-10-14T16:51:30.639Z (3 months ago)
• Language: Go
• Size: 68.4 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Code of conduct: .github/CODE_OF_CONDUCT.md
  • Codeowners: .github/CODEOWNERS

Awesome Lists containing this project

README

        
# `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

```hcl

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?