https://github.com/toowoxx/terraform-provider-packer

Terraform Provider for HashiCorp Packer
https://github.com/toowoxx/terraform-provider-packer

build cicd images packer terraform terraform-provider

Last synced: 2 months ago
JSON representation

Terraform Provider for HashiCorp Packer

• Host: GitHub
• URL: https://github.com/toowoxx/terraform-provider-packer
• Owner: toowoxx
• License: mpl-2.0
• Created: 2021-11-11T14:20:00.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2024-08-14T10:51:29.000Z (4 months ago)
• Last Synced: 2024-09-30T12:41:47.941Z (3 months ago)
• Topics: build, cicd, images, packer, terraform, terraform-provider
• Language: Go
• Homepage:
• Size: 601 KB
• Stars: 33
• Watchers: 3
• Forks: 7
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
# Terraform Packer Provider

A provider for HashiCorp Packer that has Packer embedded in it so that you can run it

on any environment (including Terraform Cloud).

## Documentation

You can find documentation in the [Terraform Registry](https://registry.terraform.io/providers/toowoxx/packer/latest/docs).

The main resource of this provider is [packer_image](https://registry.terraform.io/providers/toowoxx/packer/latest/docs/resources/image) which builds the image using packer.

## Examples

Examples can be found in the [examples subdirectory](examples/).

## Gotchas

### Image management

Packer does not manage your images – which means that neither does this provider.

This provider will **not** detect whether the image exists on the remote because that's

not something that Packer can do.

Terraform providers are only a means of plugging an API or an external system into Terraform

which is what this provider is doing.

Regardless, we still reserve the possibility that we may add support for managing images independently

of Packer itself.

You have multiple options for managing your images:

 * Import state of the created image after successful deployment

 * Manually manage images, for example, by deleting them from your cloud provider or system (for example, you can delete images manually from Azure using the Azure Portal)

You can use the `force` attribute of resource `packer_image` to overwrite the image every time.

The remote state does not affect this provider's ability to function. If you delete an image remotely, Packer will still run and attempt to create a new one which should succeed. There is no fundamental difference between "Creation" and "Update" of a `packer_image` resource.

## License

[Mozilla Public License v2.0](LICENSE)