diff --git a/website/content/docs/datasources/hcp/hcp-packer-artifact.mdx b/website/content/docs/datasources/hcp/hcp-packer-artifact.mdx new file mode 100644 index 00000000000..0261242a879 --- /dev/null +++ b/website/content/docs/datasources/hcp/hcp-packer-artifact.mdx @@ -0,0 +1,105 @@ +--- +description: | + The HCP Packer Artifact Data Source retrieves information about an + artifact from the HCP Packer Registry. This information can be used to + provide a source artifact to various Packer builders. +page_title: HCP Packer Artifact - Data Sources +--- + + + + + + +# HCP Packer Artifact Data Source + +Type: `hcp-packer-artifact` + +The `HCP Packer Artifact` Data Source retrieves information about an +artifact from the HCP Packer Registry. This information can be used to +provide a source artifact to various Packer builders. + +To get started with HCP Packer, refer to the [HCP Packer documentation](/hcp/docs/packer) or try +the [Get Started with HCP Packer tutorials](/packer/tutorials/hcp-get-started). + +~> **Note:** You will receive an error if you try to reference metadata from a deactivated or deleted registry. +An administrator can manually deactivate or delete a registry, and HCP Packer automatically deactivates registries +with billing issues. Contact [HashiCorp Support](https://support.hashicorp.com/) with questions. + +## Revoked Versions + +If an HCP Packer Version is revoked, the `hcp-packer-version` data source will fail and Packer won't proceed with +the build. Building new artifacts from a revoked artifact is not compliant. +Versions that are scheduled to be revoked will still be considered valid until the revocation date. + +## Basic Example + +Below is a fully functioning example. It stores information about an image artifact, +which can then be parsed and accessed as a variable. + +```hcl +data "hcp-packer-artifact" "example" { + bucket_name = "hardened-ubuntu-16-04" + version_fingerprint = "${data.hcp-packer-version.hardened-source.fingerprint}" + platform = "aws" + region = "us-east-1" +} +``` + +## Full Example + +This data source can be used in conjunction with the hcp-packer-version +data source to retrieve a version fingerprint using a channel. You provide the version fingerprint and channel +name to the version data source, then use the version source inside the +artifact data source, then use the artifact data source inside your source block. + +```hcl +# Retrieves information about the HCP Packer Version; a "version" can be +# thought of as all the metadata created by a single call of `packer build`. +data "hcp-packer-version" "hardened-source" { + bucket_name = "hardened-ubuntu-16-04" + channel_name = "dev" +} + +# Retrieves information about the HCP Packer Artifact; an artifact can be thought +# of as all the metadata (including the artifact names) created by a single +# "source" builder; this can include multiple artifacts so we provide a +# region to disambiguate. +data "hcp-packer-artifact" "example" { + bucket_name = "hardened-ubuntu-16-04" + version_fingerprint = data.hcp_packer_version.hardened-source.fingerprint + platform = "aws" + region = "us-east-1" +} + +# This source uses the output from a previous Packer build. By using the +# HCP Packer Registry in this way, you can easily create build pipelines where +# a single base artifact can be customized in multiple secondary layers. +source "amazon-ebs" "packer-secondary" { + source_ami = data.hcp-packer-artifact.example.external_identifier + ... +} +``` + +## Configuration Reference + +Configuration options are organized below into two categories: required and +optional. Within each category, the available options are alphabetized and +described. + +### Required: + +@include 'datasource/hcp-packer-artifact/Config-required.mdx' + +### Optional: + +~> **Note:** This data source only returns the first found artifact's metadata filtered by the given options, +from the returned list of artifacts associated with the specified version. Therefore, if multiple artifacts exist +in the same region, it will only pick one of them. In this case, you can filter artifact by a source build name +(Ex: `amazon-ebs.example`) using the `component_type` option. + +@include 'datasource/hcp-packer-artifact/Config-not-required.mdx' + +### Output Fields: + +@include 'datasource/hcp-packer-artifact/DatasourceOutput.mdx' diff --git a/website/content/docs/datasources/hcp/hcp-packer-image.mdx b/website/content/docs/datasources/hcp/hcp-packer-image.mdx index 8e1bf822337..d7312921cb4 100644 --- a/website/content/docs/datasources/hcp/hcp-packer-image.mdx +++ b/website/content/docs/datasources/hcp/hcp-packer-image.mdx @@ -1,5 +1,6 @@ --- description: | + This data source has been deprecated, please use HCP Packer Artifact data source instead. The HCP Packer Image Data Source retrieves information about an image from the HCP Packer registry. This information can be used to provide a source image to various Packer builders. @@ -8,11 +9,12 @@ page_title: HCP Packer Image - Data Sources - # HCP Packer Image Data Source +~> **Note:** This data source has been deprecated, please use [HCP Packer Artifact](/packer/docs/datasources/hcp/hcp-packer-artifact) data source instead. + Type: `hcp-packer-image` The `HCP Packer Image` Data Source retrieves information about an diff --git a/website/content/docs/datasources/hcp/hcp-packer-iteration.mdx b/website/content/docs/datasources/hcp/hcp-packer-iteration.mdx index 38c6125baee..6ad6fb3c396 100644 --- a/website/content/docs/datasources/hcp/hcp-packer-iteration.mdx +++ b/website/content/docs/datasources/hcp/hcp-packer-iteration.mdx @@ -1,5 +1,6 @@ --- description: | + This data source has been deprecated, please use HCP Packer Version data source instead. The HCP Packer Iteration Data Source retrieves information about an iteration from the HCP Packer registry. This information can be used to query HCP for a source image for various Packer builders. @@ -8,11 +9,12 @@ page_title: HCP Packer Iteration - Data Sources - # HCP Packer Iteration Data Source +~> **Note:** This data source has been deprecated, please use [HCP Packer Version](/packer/docs/datasources/hcp/hcp-packer-version) data source instead. + Type: `hcp-packer-iteration` The `HCP Packer Iteration` Data Source retrieves information about an diff --git a/website/content/docs/datasources/hcp/hcp-packer-version.mdx b/website/content/docs/datasources/hcp/hcp-packer-version.mdx new file mode 100644 index 00000000000..31b288ca4a0 --- /dev/null +++ b/website/content/docs/datasources/hcp/hcp-packer-version.mdx @@ -0,0 +1,96 @@ +--- +description: | + The HCP Packer Version Data Source retrieves information about + HCP Packer Version from the HCP Packer Registry. This information can be used to + query HCP for a source external identifier for various Packer builders. +page_title: HCP Packer Version - Data Sources +--- + + + + + + +# HCP Packer Version Data Source + +Type: `hcp-packer-version` + +The `HCP Packer Version` Data Source retrieves information about +HCP Packer Version from the HCP Packer Registry. This information can be used to +query HCP for a source external identifier for various Packer builders. + +To get started with HCP Packer, refer to the [HCP Packer documentation](/hcp/docs/packer) or try the +[Get Started with HCP Packer tutorials](/packer/tutorials/hcp-get-started). + +~> **Note:** You will receive an error if you try to reference metadata from a deactivated or deleted registry. +An administrator can manually deactivate or delete a registry, and HCP Packer automatically deactivates registries +with billing issues. Contact [HashiCorp Support](https://support.hashicorp.com/) with questions. + +## Revoked Versions + +If an HCP Packer Version is revoked, the `hcp-packer-version` data source will fail and Packer won't proceed with +the build. Building new artifacts from a revoked artifact is not compliant. +Versions that are scheduled to be revoked will still be considered valid until the revocation date. + +## Basic Example + +Below is a fully functioning example. It stores information about an HCP Packer Version, which can then be accessed as a variable. + +```hcl +data "hcp-packer-version" "hardened-source" { + bucket_name = "hardened-ubuntu-16-04" + channel_name = "dev" +} +``` + +## Full Example + +This data source can be used in conjunction with the `hcp-packer-artifact` +data source to retrieve an artifact identifier. You provide the version fingerprint and channel +name to the version data source, then use the version source inside the +artifact data source, then use the artifact data source inside your source block. + +```hcl +# Retrieves information about the HCP Packer Version; a "version" can be +# thought of as all the metadata created by a single call of `packer build`. +data "hcp-packer-version" "hardened-source" { + bucket_name = "hardened-ubuntu-16-04" + channel_name = "dev" +} + +# Retrieves information about the HCP Packer Artifact; an artifact can be thought +# of as all the metadata (including the artifact names) created by a single +# "source" builder; this can include multiple artifacts so we provide a +# region to disambiguate. +data "hcp-packer-artifact" "example" { + bucket_name = "hardened-ubuntu-16-04" + version_fingerprint = data.hcp_packer_version.hardened-source.fingerprint + platform = "aws" + region = "us-east-1" +} + +# This source uses the output from a previous Packer build. By using the +# HCP Packer Registry in this way, you can easily create build pipelines where +# a single base artifact can be customized in multiple secondary layers. +source "amazon-ebs" "packer-secondary" { + source_ami = data.hcp-packer-artifact.example.external_identifier + ... +} +``` + +## Configuration Reference + +Configuration options are organized below into two categories: required and +optional. Within each category, the available options are alphabetized and +described. + +### Required: + +@include 'datasource/hcp-packer-version/Config-required.mdx' + +There are currently no optional fields for this datasource, though we intend +to add filtering fields in the future. + +### Output Fields: + +@include 'datasource/hcp-packer-version/DatasourceOutput.mdx' diff --git a/website/content/docs/datasources/hcp/index.mdx b/website/content/docs/datasources/hcp/index.mdx index 989d3d861a1..7f5fff7616a 100644 --- a/website/content/docs/datasources/hcp/index.mdx +++ b/website/content/docs/datasources/hcp/index.mdx @@ -11,31 +11,37 @@ sidebar_title: Overview # HCP Packer Registry Data sources -The HCP Packer registry bridges the gap between image factories and image +The HCP Packer Registry bridges the gap between artifact factories and artifact deployments, allowing development and security teams to work together to create, -manage, and consume images in a centralized way. - -The HCP Packer registry stores metadata about your images, including when they -were created, where the image exists in the cloud, and what (if any) git commit -is associated with your image build. You can use the registry to track -information about the golden images your Packer builds produce, clearly -designate which images are appropriate for test and production environments, -and query for the right golden images to use in both Packer and Terraform +manage, and consume artifacts in a centralized way. + +The HCP Packer Registry stores metadata about your artifacts, including when they +were created, where the artifacts exists in the cloud, and what (if any) git commit +is associated with your build. You can use the registry to track +information about the artifacts your Packer builds produce, clearly +designate which artifacts are appropriate for test and production environments, +and query for the right artifacts to use in both Packer and Terraform configurations. Packer has two data sources that work together to retrieve information from the HCP Packer registry: +- [hcp-packer-version](/packer/docs/datasources/hcp/hcp-packer-version) - +retrieves information about an HCP Packer Version in HCP Packer Registry +- [hcp-packer-artifact](/packer/docs/datasources/hcp/hcp-packer-artifact) - retrieves +information about a specific artifact created in the HCP Packer registry + +Deprecated data sources: (Please use above given data sources instead) - [hcp-packer-iteration](/packer/docs/datasources/hcp/hcp-packer-iteration) - retrieves information about an iteration in HCP Packer registry - [hcp-packer-image](/packer/docs/datasources/hcp/hcp-packer-image) - retrieves information about a specific image created in the HCP Packer registry -These data sources are intended to be used together to determine source images +These data sources are intended to be used together to determine source artifact for pipelined Packer builds. ## How to use this plugin This plugin comes bundled with the Packer core, so you do not need to install it separately. Please install Packer v1.7.7 or above to use the latest version -of the HCP Packer registry datasources. +of the HCP Packer Registry data sources. diff --git a/website/content/docs/hcp/index.mdx b/website/content/docs/hcp/index.mdx index d908cca70cc..8063bd0dcc7 100644 --- a/website/content/docs/hcp/index.mdx +++ b/website/content/docs/hcp/index.mdx @@ -1,72 +1,120 @@ --- description: | - Packer can publish metadata for completed builds to an HCP Packer registry. Legacy JSON templates can connect to the registry using environment variables. HCL2 templates can connect using an hcp_packer_registry block. + Packer can publish metadata for completed builds to an HCP Packer Registry. Legacy JSON templates can connect to the registry using environment variables. HCL2 templates can connect using an hcp_packer_registry block. page_title: HCP Packer --- --> **Note:** On May 16th 2023, HCP introduced multi-project support to the platform. In order to use multiple projects in your organization, you will need to update Packer to version 1.9.1 or above. Starting with 1.9.1, you may specify a project ID to push builds to with the `HCP_PROJECT_ID` environment variable. If no project ID is specified, Packer will pick the project with the oldest creation date. Older versions of Packer are incompatible with multi-project support on HCP, and builds will fail for HCP organizations with multiple projects on versions before 1.9.1. +-> **Note:** On May 16th 2023, HCP introduced multi-project support to the platform. In order to use multiple projects +in your organization, you will need to update Packer to version 1.9.1 or above. Starting with 1.9.1, you may specify +a project ID to push builds to with the `HCP_PROJECT_ID` environment variable. If no project ID is specified, +Packer will pick the project with the oldest creation date. Older versions of Packer are incompatible with multi-project +support on HCP, and builds will fail for HCP organizations with multiple projects on versions before 1.9.1. # HCP Packer -The HCP Packer registry bridges the gap between image factories and image deployments, allowing development and security teams to work together to create, manage, and consume images in a centralized way. +The HCP Packer registry bridges the gap between artifact factories and artifact deployments, allowing development and +security teams to work together to create, manage, and consume artifacts in a centralized way. -The HCP Packer registry stores metadata about your images, including when they were created, where the image exists in the cloud, and what (if any) git commit is associated with your image build. You can use the registry to track information about the golden images your Packer builds produce, clearly designate which images are appropriate for test and production environments, and query for the right golden images to use in both Packer and Terraform configurations. +The HCP Packer Registry stores metadata about your artifact, including when they were created, where the artifact +exists on the external platform, and what (if any) git commit is associated with your build. You can use the registry +to track information about the artifact your Packer builds produce, clearly designate which artifact are appropriate +for test and production environments, and query for the right artifact to use in both Packer and Terraform +configurations. -You can use HCP Packer with both JSON and HCL2 templates. If you are using JSON templates, we recommend getting started with -the [HCP Packer environment variables](#hcp-packer-environment-variables) and then migrating to HCL when possible. +You can use HCP Packer with both JSON and HCL2 templates. If you are using JSON templates, we recommend getting started with +the [HCP Packer environment variables](#hcp-packer-environment-variables) and then migrating to HCL when possible. -This page summarizes the methods you can use to connect JSON and HCL2 templates to the HCP Packer registry. It also provides a full list of HCP Packer environment variables. Refer to the [Packer Template Configuration](/hcp/docs/packer/store-image-metadata/packer-template-configuration) page in the HCP Packer documentation for full configuration details and examples. +This page summarizes the methods you can use to connect JSON and HCL2 templates to the HCP Packer registry. It also +provides a full list of HCP Packer environment variables. Refer to the +[Packer Template Configuration](/hcp/docs/packer/store-image-metadata/packer-template-configuration) page in the HCP +Packer documentation for full configuration details and examples. ### HCP Packer Environment Variables -The following environment variables let you configure Packer to push image metadata to an active registry without changing your template. You can use environment variables with both JSON and HCL2 templates. Refer to [Basic Configuration With Environment Variables](/hcp/docs/packer/store-image-metadata/packer-template-configuration#basic-configuration-with-environment-variables) in the HCP Packer documentation for complete instructions and examples. +The following environment variables let you configure Packer to push artifact metadata to an active registry without +changing your template. You can use environment variables with both JSON and HCL2 templates. +Refer to [Basic Configuration With Environment Variables](/hcp/docs/packer/store-image-metadata/packer-template-configuration#basic-configuration-with-environment-variables) +in the HCP Packer documentation for complete instructions and examples. You must set the following environment variables to enable Packer to push metadata to a registry. -- `HCP_CLIENT_ID` - The HCP client ID of a HashiCorp Cloud Platform service principle that Packer can use to authenticate to an HCP Packer registry. +- `HCP_CLIENT_ID` - The HCP client ID of a HashiCorp Cloud Platform service principle that Packer can use to +authenticate to an HCP Packer Registry. -- `HCP_CLIENT_SECRET` - The HCP client secret of the HashiCorp Cloud Platform service principle that Packer can use to authenticate to an HCP Packer registry. +- `HCP_CLIENT_SECRET` - The HCP client secret of the HashiCorp Cloud Platform service principle that Packer +can use to authenticate to an HCP Packer Registry. -- `HCP_PACKER_BUCKET_NAME` - The name of the image bucket where you want HCP Packer to store image metadata from builds associated with your template. HCP Packer automatically creates the image bucket if it does not already exist. If your HCL2 template contains an `hcp_packer_registry` block, the bucket name specified in the configuration will be overwritten by this environment variable. +- `HCP_PACKER_BUCKET_NAME` - The name of the HCP Packer Bucket where you want HCP Packer to store artifact metadata +from builds associated with your template. HCP Packer automatically creates the bucket if it does not already exist. +If your HCL2 template contains an `hcp_packer_registry` block, the bucket name specified in the configuration will be +overwritten by this environment variable. You can set these additional environment variables to control how metadata is pushed to the registry. -- `HCP_PACKER_BUILD_FINGERPRINT` - A unique identifier assigned to each iteration. To reuse a fingerprint that is associated with an existing incomplete iteration you must set this environment variable. Refer to [Iteration Fingerprinting](#iteration-fingerprinting) for usage details. +- `HCP_PACKER_BUILD_FINGERPRINT` - A unique identifier assigned to each version. To reuse a fingerprint that is +associated with an existing incomplete version you must set this environment variable. Refer to +[Version Fingerprinting](#version-fingerprinting) for usage details. -- `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_REGISTRY` - When set, Packer does not push artifact metadata to HCP Packer from an otherwise +configured template. Allowed values are [0|OFF]. -- `HCP_ORGANIZATION_ID` - The ID of the HCP organization linked to your service principal. This is environment variable is not required and available for the sole purpose of keeping parity with the HCP SDK authentication options. Its use may change in a future release. +- `HCP_ORGANIZATION_ID` - The ID of the HCP organization linked to your service principal. This is environment +variable is not required and available for the sole purpose of keeping parity with the HCP SDK authentication options. +Its use may change in a future release. -- `HCP_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. +- `HCP_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_PROJECT_ID environment variable must be set if you're authenticating with a project-level service principal, otherwise Packer will attempt to get the list of projects for an organization and error due to a lack of permissions for a project-level service principal. This is supported starting with Packer 1.9.3; older versions of Packer do not support using project-level service principals. +-> **Note**: The HCP_PROJECT_ID environment variable must be set if you're authenticating with a project-level service +principal, otherwise Packer will attempt to get the list of projects for an organization and error due to a lack of +permissions for a project-level service principal. This is supported starting with Packer 1.9.3; older versions of +Packer do not support using project-level service principals. ### HCP Packer Registry Block -The only metadata that Packer can infer from a template with the basic configuration are the build name and build fingerprint. For HCL2 templates, we recommend adding the `hcp_packer_registry` block to your template so that you can customize the metadata that Packer sends to the registry. +The only metadata that Packer can infer from a template with the basic configuration are the build name and build fingerprint. +For HCL2 templates, we recommend adding the `hcp_packer_registry` block to your template so that you can customize +the metadata that Packer sends to the registry. The `hcp_packer_registry` block is only available for HCL2 Packer templates. There is no [`PACKER_CONFIG`](/packer/docs/configure#packer-s-config-file) equivalent for JSON. -Refer to [`hcp_packer_registry`](/packer/docs/templates/hcl_templates/blocks/build/hcp_packer_registry) for a full list of configuration arguments. Refer to [Custom Configuration](/hcp/docs/packer/store-image-metadata/packer-template-configuration#custom-configuration) in the HCP Packer documentation for information and examples about how to customize image metadata. +Refer to [`hcp_packer_registry`](/packer/docs/templates/hcl_templates/blocks/build/hcp_packer_registry) for a full list +of configuration arguments. Refer to [Custom Configuration](/hcp/docs/packer/store-image-metadata/packer-template-configuration#custom-configuration) +in the HCP Packer documentation for information and examples about how to customize artifact metadata. -### Iteration Fingerprinting +### Version Fingerprinting -Packer uses a unique fingerprint for tracking the completion of builds associated to an iteration. By default a fingerprint is automatically generated by Packer during each invocation of `packer build`, unless a fingerprint is manually provided via the `HCP_PACKER_BUILD_FINGERPRINT` environment variable. +Packer uses a unique fingerprint for tracking the completion of builds associated to a version. By default a fingerprint +is automatically generated by Packer during each invocation of `packer build`, unless a fingerprint is manually provided +via the `HCP_PACKER_BUILD_FINGERPRINT` environment variable. -In versions before 1.9.0, this fingerprint was computed from the Git SHA of the current HEAD in which your template is stored. If you were running builds using a non Git managed template, you had to set the `HCP_PACKER_BUILD_FINGERPRINT` environment variable prior to invoking `packer build`. -Starting with Packer 1.9.0, fingerprint generation does not rely on Git at all, and instead Packer now generates a Unique Lexicographically sortable Identifier (ULID) as the fingerprint for every `packer build` invocation. +In versions before 1.9.0, this fingerprint was computed from the Git SHA of the current HEAD in which your template is +stored. If you were running builds using a non Git managed template, you had to set the `HCP_PACKER_BUILD_FINGERPRINT` +environment variable prior to invoking `packer build`. +Starting with Packer 1.9.0, fingerprint generation does not rely on Git at all, and instead Packer now generates +a Unique Lexicographically sortable Identifier (ULID) as the fingerprint for every `packer build` invocation. -#### Fingerprints and Incomplete Iterations +#### Fingerprints and Incomplete Versions -When you build a template with Packer, there's always a chance that it does not succeed because of a network issue, a provisioning failure, or some upstream error. When that happens, Packer will output the generated fingerprint associated with the incomplete iteration so that you can resume building that iteration using the `HCP_PACKER_BUILD_FINGERPRINT` environment variable; an iteration can be resumed until it is marked as complete. This environment variable is necessary for resuming an incomplete iteration, otherwise Packer will create a new iteration for the build. +When you build a template with Packer, there's always a chance that it does not succeed because of a network issue, +a provisioning failure, or some upstream error. When that happens, Packer will output the generated fingerprint +associated with the incomplete version so that you can resume building that version using the `HCP_PACKER_BUILD_FINGERPRINT` +environment variable; a version can be resumed until it is marked as complete. This environment variable is necessary +for resuming an incomplete version, otherwise Packer will create a new version for the build. There are two alternatives for when and how to set your own fingerprint: -* You can set it prior to invoking `packer build` for the first time on this template. This will require the fingerprint to be unique, otherwise Packer will attempt to continue the iteration with the same fingerprint. -* You can invoke `packer build` on the template, and if it fails, you can then get the fingerprint from the output of the command and set it for subsequent runs, Packer will then continue building this iteration. +* You can set it prior to invoking `packer build` for the first time on this template. This will require the +fingerprint to be unique, otherwise Packer will attempt to continue the version with the same fingerprint. +* You can invoke `packer build` on the template, and if it fails, you can then get the fingerprint from the output of +the command and set it for subsequent runs, Packer will then continue building this version. -The first alternative is recommended for CI environments, as you can use environment variables from the CI to generate a unique, deterministic, fingerprint, and then re-use this in case the step fails for any reason. This will let you continue building the same iteration, rather than creating a new one on each invocation. +The first alternative is recommended for CI environments, as you can use environment variables from the CI to generate +a unique, deterministic, fingerprint, and then re-use this in case the step fails for any reason. This will let you +continue building the same version, rather than creating a new one on each invocation. -The second alternative is good for local builds, as you can interact with the build environment directly, and therefore can decide if you want to continue building an iteration by setting the fingerprint provided by Packer in case of failure. +The second alternative is good for local builds, as you can interact with the build environment directly, and therefore +can decide if you want to continue building a version by setting the fingerprint provided by Packer in case of failure. -Please note that in all cases, an iteration can only be continued if it has not completed yet. Once an iteration is complete, it cannot be modified, and you will have to create a new one. +Please note that in all cases, a version can only be continued if it has not completed yet. Once a version is +complete, it cannot be modified, and you will have to create a new one. diff --git a/website/content/docs/index.mdx b/website/content/docs/index.mdx index 5fd386e1dc7..b4ab7cf0cd6 100644 --- a/website/content/docs/index.mdx +++ b/website/content/docs/index.mdx @@ -12,6 +12,8 @@ To install Packer and learn the standard Packer workflow, try the [Get Started t ## HCP Packer -The HCP Packer registry stores metadata about your images. You can use the registry to track information about golden images from your Packer builds, clearly designate which images are appropriate for test and production environments, and query for the right images to use in both Packer and Terraform configurations. +The HCP Packer registry stores metadata about your artifacts. You can use the registry to track information about +artifacts from your Packer builds, clearly designate which artifacts are appropriate for test and production +environments, and query for the right artifacts to use in both Packer and Terraform configurations. To get started, visit the [HCP Packer documentation](/hcp/docs/packer) or try the [Get Started with HCP Packer tutorials](/packer/tutorials/hcp-get-started). diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json index 7c7e110d518..807fb16f968 100644 --- a/website/data/docs-nav-data.json +++ b/website/data/docs-nav-data.json @@ -729,6 +729,14 @@ "title": "Overview", "path": "datasources/hcp" }, + { + "title": "Version", + "path": "datasources/hcp/hcp-packer-version" + }, + { + "title": "Artifact", + "path": "datasources/hcp/hcp-packer-artifact" + }, { "title": "Iteration", "path": "datasources/hcp/hcp-packer-iteration"