packer

Commit Graph

Author	SHA1	Message	Date
Wilken Rivera	0053fed683	backport of commit `f568b68b92`	3 years ago
Lucas Bajolet	86e70ee7f1	backport of commit `3ca74ccca8`	3 years ago
Lucas Bajolet	ffd229d411	backport of commit `a7e5e07503`	3 years ago
Ashlee M Boyer	50da6c8dc8	docs: Migrate link formats (#12192 ) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Migrating links to new format * Updating docs-content-check-legacy-links-format hash * chore: update source * Update generated partials from Packer plugin SDK * Bump packer-plugin-sdk to get latest packer-sdc * Update website/content/docs/templates/hcl_templates/blocks/build/provisioner.mdx * Update Plugin SDK to fix shell-local regression --------- Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com> Co-authored-by: Wilken Rivera <wilken@hashicorp.com> Co-authored-by: Kendall Strautman <36613477+kendallstrautman@users.noreply.github.com>	3 years ago
Lucas Bajolet	ec1d2e68f5	hcp: generate fingerprints on each new build Fingerprints are how we link a packer build to an iteration on HCP. These are computed automatically from the Git SHA in the current state, and are unique to the bucket/iteration. The main problem with this approach is that while sound in theory, it quickly falls apart when users want to run the same build configuration twice, but expect a new image to be created. With the current model, this fails, as the iteration with the current SHA already exists. While this is solvable through environment variables, or by committing a change to the repository, we think this is not clear enough, and causes an extra step to what should otherwise be a simple process. Therefore, to lower the barrier of entry into HCP, we change this behaviour with this commit. Now, fingerprints are randomly generated ULIDs instead of a git SHA, and a new one is always generated, unless one is already specified in the environment. This makes continuation of an existing iteration a conscious choice rather than something automatic, and virtually eliminates conflicts such as the ones described above.	3 years ago
Wilken Rivera	1296cbfc92	Update links to packer-template-configuration (#12072 )	4 years ago
Wilken Rivera	414b576def	[HPR-574] Add documentation for configuring Packer for HCP Packer (#12022 ) * Add documentation for configuring Packer for HCP Packer This change works to document the two configuration options for setting up Packer to publish build artifacts to an active HCP Packer registry. Currently the HashiCorp Cloud Platform documents the process for configuring Packer via a HCL template, which is the preferred route. This documentation focuses more on the use of environment variables for configuring Packer for HCP Packer, which is necessary for legacy JSON template users looking to publish to HCP Packer. In light of the new HCP Packer documentation page we've opted for a shorter version of the HCP Packer introduction section. * Applying the first round of suggestions to tighten up the documentation. * Move HCP Packer side bar to top * Move intro into docs * Add redirects for intro pages Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	4 years ago

7 Commits (620fb4983dda40db15c1b5b0be21f7ad0c0bbdbb)