packer

Commit Graph

Author	SHA1	Message	Date
Leah Bush	e9d220436d	feat: add docs to packer docs	5 months ago
Jenna Goldstrich	40bea58c92	Fix incorrect Credential file default path in docs (#13447 ) should be ~/.config/hcp/cred_file.json	8 months ago
Jenna Goldstrich	8a376a8845	HCP Certificate Authentication Support (#13435 ) * Add support for using a certificate file instead of HCP Client Credentials to authenticate to HashiCorp Cloud Platform * Docs * Change certificate auth warnings to print to stdio * rough draft docs * Update comments * Parse home directory correctly, default directory certs don't work before this * cred-file => cred_file, and add unit test * Fix invalid log, and use full path in log messages and error messages * Fix original file not being reset in unit test * Move test statements around to validate Windows behavior * Use a 'windows friendly' path * The issue here was the path error'd on mac and linux, but not Windows, when I swapped to the different path then nothing error'd causing everything to fail, I think this should fix it on 3 platforms * 1.14.1 => 1.14.2	8 months ago
trujillo-adam	9fd83c155c	Apply suggestions from code review Co-authored-by: Brian McClain <brianmmcclain@gmail.com>	1 year ago
trujillo-adam	da35666689	buiders, plugins, and some top-level pages	1 year ago
Devashish	3fa637c608	Migrate HCP Packer to API V2 and new nomenclature changes (#12794 ) * add hcp packer new nomenclature updates * Update docs with nomenclature changes * Update navigation bar links * Bump github.com/hashicorp/hcp-sdk-go from 0.81.0 to 0.82.0 * fix acceptance test template --------- Co-authored-by: sylviamoss <moss@hashicorp.com> Co-authored-by: Wilken Rivera <dev@wilkenrivera.com>	2 years ago
Lucas Bajolet	2b32903fe3	Document PLSP-related environment variables Since we added support for PLSPs recently, and it will be released as part of 1.9.3, we add some documentation regarding the environment variables we added, and a note regarding their relation to PLSP support.	3 years ago
Lucas Bajolet	aeffaa790f	docs: add a paragraph on fingerprint generation (#12464 ) * docs: add a paragraph on fingerprint generation Since version 1.9.0+ changed the way Packer generates fingerprints for HCP Packer, we add a small paragraph to explain how it used to be generated before, and how it changed in this version. * Apply suggestions from code review --------- Co-authored-by: Wilken Rivera <wilken@hashicorp.com>	3 years ago
Lucas Bajolet	925cb5e541	hcp: support HCP_PROJECT_ID environment variable With HCP supporting multi-projects now, Packer needs to take it into account when picking a project from an organisation. This commit adds two cases: 1. multiple projects are defined, none is supplied through HCP_PROJECT_ID: in this case we will default to the oldest project defined for the organisation. 2. we supply HCP_PROJECT_ID: in this case, we pick the project with the corresponding ID, and use it for publishing metadata.	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

13 Commits (mod-update)