packer

Commit Graph

Author	SHA1	Message	Date
Lucas Bajolet	548893bbee	build: don't suggest lack of HCP support on fail When running a build with HCP Packer enabled, Packer attempts to push the build status to HCP. If the build fails, we update the status to BUILD_FAILED, and that's the end of it. If however the build succeeds, Packer attempts to get the HCP artifact from the builder, which will only succeed if the builder supports it. Otherwise, we'll get either nil, or an artifact type that is not compatible with what is expected for HCP support. When either of those happens, we warn that the builder may not support HCP Packer at all, so users are aware of the problem. However, when the error was introduced, it only looked at the fact that an error was produced, independently of the type of error. This caused legitimate errors while building to be reported as potential incompatibility between the builder and HCP, which was confusing to users. This commit changes this by introducing a new error type, only produced when the artifact either is nil, or failed to be deserialised into a HCP artifact, which lets us produce the incompatibility warning with more accuracy.	2 years ago
dependabot[bot]	9b01bfa486	build(deps): bump github.com/hashicorp/hcp-sdk-go from 0.82.0 to 0.83.0 (#12827 ) Bumps [github.com/hashicorp/hcp-sdk-go](https://github.com/hashicorp/hcp-sdk-go) from 0.82.0 to 0.83.0. - [Release notes](https://github.com/hashicorp/hcp-sdk-go/releases) - [Changelog](https://github.com/hashicorp/hcp-sdk-go/blob/main/CHANGELOG.md) - [Commits](https://github.com/hashicorp/hcp-sdk-go/compare/v0.82.0...v0.83.0) --- updated-dependencies: - dependency-name: github.com/hashicorp/hcp-sdk-go dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2 years ago
Wilken Rivera	4d38323ae1	Remove external Plugins from left navbar	2 years ago
Lucas Bajolet	dff49df129	hcl2template: check bucket name at parse-time Not validating the bucket's name during parse leads to configurations being marked as valid, even if the bucket name is not, which will fail during a real build afterwards. To avoid this problem and fail with an error as quickly as possible, we add a check during parsing, so that it gets reported for validate as well.	2 years ago
Heat Hamilton	767005149c	website: fix husky command (#12821 ) * Change husky pre-commit hook to work in sub-directory of .git * Added dart-linkcheck back in for linkcheck command	2 years ago
Wilken Rivera	08d41c2679	Fix URL rewrite check error for DevDot portal (#12818 ) Refer to job https://github.com/hashicorp/packer/actions/runs/7709708630/job/21011464094	2 years ago
Wilken Rivera	ca066f73bf	Update CHANGELOG	2 years ago
Wilken Rivera	1e6041ab05	docs/plugins:Fix incorrect plugin directory path	2 years ago
Heat Hamilton	ec403555dc	Updated next, node, npm, nvmrc and Docker node versions; added husky pre-commit hook v9	2 years ago
Wilken Rivera	da65323918	Remove all external plugin docs This change removes all external plugin docs using the old remote docs framework from the Packer core documentation in favor of the Packer integration framework. Remove plugins will be enabled on the integration portal and contacted to merge their PRs to finalize the integration migration.	2 years ago
Devashish	682eca2877	Remove repeated code	2 years ago
Devashish	4b591d6937	Add PR suggestions	2 years ago
Devashish	14ce2a559c	fix shell session in the docs	2 years ago
Devashish	b77d581cda	Add the deprecation warning and update docs	2 years ago
Devashish	cbc16cfed5	Add versionFingerprint to EvalContext	2 years ago
Devashish	91ce35f439	Expose versionFingerprint instead of versionId from packer template	2 years ago
Wilken Rivera	12b8c885a3	Update error messaging for HCP incompatible plugin builds (#12800 ) * Update error messaging for HCP incompatible plugin builds * Update command/build.go Co-authored-by: Lucas Bajolet <105649352+lbajolet-hashicorp@users.noreply.github.com> --------- Co-authored-by: Lucas Bajolet <105649352+lbajolet-hashicorp@users.noreply.github.com>	2 years 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
dependabot[bot]	91ce018cf1	build(deps): bump github.com/hashicorp/hcp-sdk-go from 0.79.0 to 0.81.0 Bumps [github.com/hashicorp/hcp-sdk-go](https://github.com/hashicorp/hcp-sdk-go) from 0.79.0 to 0.81.0. - [Release notes](https://github.com/hashicorp/hcp-sdk-go/releases) - [Changelog](https://github.com/hashicorp/hcp-sdk-go/blob/main/CHANGELOG.md) - [Commits](https://github.com/hashicorp/hcp-sdk-go/compare/v0.79.0...v0.81.0) --- updated-dependencies: - dependency-name: github.com/hashicorp/hcp-sdk-go dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>	2 years ago
Wilken Rivera	96755d2f7b	Remove migrated integrations from plugin manifest This change removes Scaleway and Mondoo from the external plugins manifest in favor of the integration framework, which they have migrated to.	2 years ago
Lucas Bajolet	6c99f387a0	packer: remove single-component plugins Single-component plugins are a relic from the past that has been deprecated from version 1.7.0 and onwards. Since we're revisiting how plugins are installed/loaded, and the changes will be incompatible with those, we remove them in preparation of this work.	2 years ago
Wilken Rivera	beb5fcf470	Bump github.com/cloudflare/circl to address GHSA-9763-4f94-gfch (#12781 )	2 years ago
dependabot[bot]	a9000f3a70	build(deps): bump github.com/hashicorp/hcp-sdk-go from 0.74.0 to 0.79.0 Bumps [github.com/hashicorp/hcp-sdk-go](https://github.com/hashicorp/hcp-sdk-go) from 0.74.0 to 0.79.0. - [Release notes](https://github.com/hashicorp/hcp-sdk-go/releases) - [Changelog](https://github.com/hashicorp/hcp-sdk-go/blob/main/CHANGELOG.md) - [Commits](https://github.com/hashicorp/hcp-sdk-go/compare/v0.74.0...v0.79.0) --- updated-dependencies: - dependency-name: github.com/hashicorp/hcp-sdk-go dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>	2 years ago
Wilken Rivera	bfc3f8b564	Bump github.com/go-git/go-git/v5 to address CVE-2023-49568	2 years ago
Wilken Rivera	2515aa27a7	Bump golang.org/x/crypto to address CVE-2023-48795	2 years ago
Wilken Rivera	0a64a5fb90	Bump Go version to 1.20.12 Bumped to pull in security fixes to the go command, the net/http package, and path/filepath package.	2 years ago
Aidan Mundy	0b06cb58a3	Fix Typo `make check-generate` -> `make generate-check`	2 years ago
Lucas Bajolet	311a3b1d6a	website: remove UpCloud from manifest Since the UpCloud plugin has moved to the integrations model, we don't want to continue looking for a docs.zip in their repo, as it doesn't exist anymore with this migration.	2 years ago
Brian McClain	76de1d3fc0	Merge pull request #12767 from hashicorp/bmm/upcloud-version-pin Pin UpCloud plugin version	2 years ago
Brian McClain	9afafd962f	Pin UpCloud plugin version	2 years ago
hc-github-team-es-release-engineering	4825c65234	Merge pull request #12752 from hashicorp/RELPLAT-955-EOY-license-updates [DO NOT MERGE UNTIL EOY] EOY license updates	2 years ago
Wilken Rivera	699c0f814c	Update plugin_integration.md Fix todo list markdown formatting	2 years ago
hc-github-team-es-release-engineering	fd7fc49f17	update year in license files	2 years ago
Wilken Rivera	2241b1fba7	Update spacing for flags within Help text Before Change ``` Options: - path <path>: install the plugin from a locally-sourced plugin binary. This installs the plugin where a normal invocation would, but will not try to download it from a remote location, and instead install the binary in the Packer plugins path. This option cannot be specified with a version constraint. - force: forces reinstallation of plugins, even if already installed. ``` After Change ``` Options: -path <path> Install the plugin from a locally-sourced plugin binary. This installs the plugin where a normal invocation would, but will not try to download it from a remote location, and instead install the binary in the Packer plugins path. This option cannot be specified with a version constraint. -force Forces reinstallation of plugins, even if already installed. ```	2 years ago
Wilken Rivera	9d46c90c03	Apply suggestions from code review Co-authored-by: Lucas Bajolet <105649352+lbajolet-hashicorp@users.noreply.github.com> Co-authored-by: Sylvia Moss <moss@hashicorp.com>	2 years ago
Wilken Rivera	9565eca354	Remove reference to deprecated single components	2 years ago
Wilken Rivera	e2a2a08f56	Add example shell commands for copying integration files into plugin repository	2 years ago
Wilken Rivera	149a8095e1	Address review feedback	2 years ago
Wilken Rivera	6d7d266bb6	Replace relative links	2 years ago
Wilken Rivera	c0de07c32e	Document process for registering a plugin as a Packer Integration	2 years ago
Wilken Rivera	4d5f1a3607	Update CHANGELOG for 1.10.0 release	2 years ago
Lucas Bajolet	da97f46958	plugin-getter: don't rely only on version for list The plugins installed command list installed plugins, and prints out all their paths and versions. The results are listed in a list of unique versions, in ascending order. When listing plugins outside of a specific identifier however, because of the insertion in the list works, we only consider the version number, and ignore all subsequent insertions with the same version. This causes a problem when we have multiple plugins installed with the same version, as only the first one that is discovered (typically the one with lexicographical precedence) gets inserted, and the others are ignored. To support such a use case, we change the insertion routine to not only support versions, but also paths when finding a spot to insert the installation into.	2 years ago
Wilken Rivera	91a16aa8e0	Remove migrated plugins from old plugin docs framework This change removes the following plugins from the old docs framework, as they have been fully migrated to the integrations framework. * ethanmdavidson/packer-plugin-git * linode/packer-plugin-linode * parallels/packer-plugin-parallels * ivoronin/packer-plugin-sshkey * cirruslabs/packer-plugin-tart	2 years ago
Lucas Bajolet	97e2e9e637	docs: add exerpt on packer plugins install --path	2 years ago
Lucas Bajolet	8e2a22e583	command: simplify local binary installation Read original binary into memory to fix case when installation destination and source were the same, resulting in an empty binary.	2 years ago
Lucas Bajolet	e293f2d890	command: plugins install reject non-releases When installing a plugin with packer plugins install --path, we only accept release versions of a plugin, as otherwise the loading can be inconsistent if for example a user specifies a required_plugins block in their template, in which case the plugins will be ignored. Until we have a simpler loading scheme then, we will reject non-release versions of plugins to avoid confusion.	2 years ago
Lucas Bajolet	ae5b91864c	command: reject version with --path for install To avoid plugins being installed with a specific version when a path is used for installing a plugin from a locally sourced plugin binary, we explicitly reject the combination of both a path and a version for plugins install.	2 years ago
Lucas Bajolet	a2d9c9dce4	command: add --force option to init/install The --force option for packer init and packer plugins install enforces installation of a plugin, even if it is already locally installed. This will become useful if for some reason a pre-existing plugin binary/version is already installed, and we want to overwrite it.	2 years ago
Lucas Bajolet	6f43a82e02	command: add packer plugins install path flag This new flag allows the `packer plugins install' command to install a plugin from a local binary rather than from Github. This command will only call `describe' on the plugin, and won't do any further checks for functionality. The SHA256SUM will be directly computed from the binary, so as with anything manual and potentially sourced by the community, extra care should be applied when invoking this.	2 years ago
Wilken Rivera	327d8a4f73	Update CHANGELOG for upcoming releases	2 years ago

1 2 3 4 5 ...

18382 Commits (548893bbee4e5a49bbbb07a81d19b2e2641fa421) All Branches Search

18382 Commits (548893bbee4e5a49bbbb07a81d19b2e2641fa421)

All Branches