No description
  • Go 85.8%
  • MDX 10.4%
  • HCL 2.3%
  • Shell 1.2%
  • Makefile 0.3%
Find a file
Tanmay Jain 2657ce0dcf
Merge pull request #339 from hashicorp/authorization-bypass
Update dependencies in go.mod and go.sum
2026-03-28 18:04:48 +05:30
.github Bump x/crypto to v0.46.0 2025-12-09 12:13:50 +05:30
.release Updated Slack Release Channel ID 2025-10-15 10:55:07 +05:30
.web-docs Add support for Secure Tags 2026-02-12 15:26:40 +01:00
builder/googlecompute Merge pull request #331 from rosmo/add-resource-manager-tags 2026-03-11 17:07:15 +05:30
datasource [COMPLIANCE] Update Copyright and License Headers (Batch 1 of 1) 2025-12-08 12:15:00 +00:00
docs Resolving typo in docs 2025-09-29 17:28:59 +05:30
docs-partials Add support for Secure Tags 2026-02-12 15:26:40 +01:00
example [COMPLIANCE] Update Copyright and License Headers (Batch 1 of 1) 2025-12-08 12:15:00 +00:00
lib/common Add support for Secure Tags 2026-02-12 15:26:40 +01:00
post-processor Merge pull request #318 from rogerhu/rogerh/ISSUE-113 2026-01-03 16:46:43 +05:30
version version: prepare v1.2.6 2026-01-28 12:01:18 +05:30
.gitignore gitignore: add crash.log to gitignore 2023-04-18 16:39:51 -04:00
.go-version Bump x/crypto to v0.46.0 2025-12-09 12:13:50 +05:30
.golangci.yml golangci-lint: update config file to conform with 1.61.0 changes 2025-04-09 10:55:55 -04:00
CHANGELOG.md version: cut release 1.2.5 2026-01-27 23:50:37 +05:30
CODEOWNERS Managed by Terraform: Update CODEOWNERS 2021-04-27 09:35:18 -04:00
GNUmakefile GNUmakefile: make dev uses packer for install (#213) 2024-04-16 11:11:00 -04:00
go.mod Update dependencies in go.mod and go.sum 2026-03-28 17:55:33 +05:30
go.sum Update dependencies in go.mod and go.sum 2026-03-28 17:55:33 +05:30
LICENSE [COMPLIANCE] Update Copyright and License Headers (Batch 1 of 1) 2025-12-08 12:15:00 +00:00
main.go [COMPLIANCE] Update Copyright and License Headers (Batch 1 of 1) 2025-12-08 12:15:00 +00:00
manifest.json Merge pull request #291 from hashicorp/crt-migration 2025-08-04 11:22:30 +05:30
README.md version: cut release 1.2.5 2026-01-27 23:50:37 +05:30

Packer Plugin Googlecompute

The Googlecompute multi-component plugin can be used with HashiCorp Packer to create custom images. For the full list of available features for this plugin see docs.

Installation

Using pre-built releases

Using the packer init command

Starting from version 1.7, Packer supports a new packer init command allowing automatic installation of Packer plugins. Read the Packer documentation for more information.

To install this plugin, copy and paste this code into your Packer configuration . Then, run packer init.

packer {
  required_plugins {
    googlecompute = {
      version = ">= 1.2.5"
      source  = "github.com/hashicorp/googlecompute"
    }
  }
}

Note: Update to Packer Plugin Installation

With the new Packer release starting from version v1.14.0, the packer init command will automatically install official plugins from the HashiCorp release site.

Going forward, to use newer versions of official Packer plugins, you'll need to upgrade to Packer version 1.14.0 or later. If you're using an older version, you can still install plugins, but as a workaround, you'll need to manually install them using the CLI.

There is no change to the syntax or commands for installing plugins.

Manual installation

You can find pre-built binary releases of the plugin here. Once you have downloaded the latest archive corresponding to your target OS, uncompress it to retrieve the plugin binary file corresponding to your platform. To install the plugin, please follow the Packer documentation on installing a plugin.

From Sources

If you prefer to build the plugin from sources, clone the GitHub repository locally and run the command go build from the root directory. Upon successful compilation, a packer-plugin-googlecompute plugin binary file can be found in the root directory. To install the compiled plugin, please follow the official Packer documentation on installing a plugin.

Configuration

For more information on how to configure the plugin, please read the documentation located in the docs/ directory.

Contributing

  • If you think you've found a bug in the code or you have a question regarding the usage of this software, please reach out to us by opening an issue in this GitHub repository.
  • Contributions to this project are welcome: if you want to add a feature or a fix a bug, please do so by opening a Pull Request in this GitHub repository. In case of feature contribution, we kindly ask you to open an issue to discuss it beforehand.