From 4bac593e7c1b88da334f3789c9ab34a15c9a953e Mon Sep 17 00:00:00 2001 From: Lucas Bajolet Date: Wed, 16 Aug 2023 14:47:43 +0000 Subject: [PATCH] backport of commit 56527bce8e3ae90e03d92dd1f04fd19aeb5282e1 --- website/content/docs/hcp/index.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/content/docs/hcp/index.mdx b/website/content/docs/hcp/index.mdx index c2ec3d4b4..1458a4309 100644 --- a/website/content/docs/hcp/index.mdx +++ b/website/content/docs/hcp/index.mdx @@ -35,6 +35,8 @@ You can set these additional environment variables to control how metadata is pu - `HCP_PACKER_REGISTRY` - When set, Packer does not push image metadata to HCP Packer from an otherwise configured template. Allowed values are [0|OFF]. +- `HCP_PACKER_ORGANIZATION_ID` - The ID of the HCP organization linked to your service principal. + - `HCP_PACKER_PROJECT_ID` - The ID of the HCP project to use. This is useful if your service principal has access to multiple projects, as by default Packer will pick the one created first as target. -> **Note**: The HCP_PACKER_PROJECT_ID environment variable must be set if you're authenticating with a project-level service principal, as otherwise Packer will attempt to get the list of projects for an organization, which will error due to a lack of permissions. This is supported starting with Packer 1.9.3; older versions of Packer do not support using project-level service principals.