7 Commits (backport-changes)

Author	SHA1	Message	Date
hashicorp-copywrite[bot]	6af0b29558	[COMPLIANCE] Update Copyright and License Headers	5 months ago
Wilken Rivera	c245b1fb7c	deps: Bump github.com/hashicorp/hcp-sdk-go to v0.73.0 ... * Updates cloud-resource-management API to use sable * Removes duplicate imports of the same SDK packages	2 years ago
hashicorp-copywrite[bot]	19055df3ec	[COMPLIANCE] License changes (#12568) ... * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at https://hashi.co/bsl-blog, FAQ at https://hashi.co/license-faq, and details of the license at www.hashicorp.com/bsl. * Update copyright file headers to BUSL-1.1 --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
Wilken Rivera	60c66fdf9f	Add additional validation for manually set project ids ... When setting a project id via the HCP_PROJECT_ID env the client will try to validate the project by checking that it has an associated registry. If the project is invalid or not a valid UUID an error will be displayed to the user * Add comment to clarify usage of SDK loaded env. variables	3 years ago
Wilken Rivera	38101a64c9	hcp: Add support for project level service principals ... HCP supports two types of service principals: Organization-level and project-level. When a user tries to publish to an active HCP Packer registry using a plsp the client fails when configuring the client due to a API permission error; namely plsp do not have the permissions to query an org for a list of projects. Setting the HCP_PROJECT_ID does not resolve the issue because the call to ListProjects is still executed. This changes updates the client configuration params to obtain both the HCP Organization and Project IDs that will be used for connecting to the HCP Packer registry. With this change if a user provides a project Id via the HCP_PROJECT_ID environment variable no call to ListProjects will be made. Instead the value will be take as is and used to create the connection. A user connecting with a project level service principals must provide a valid HCP_PROJECT_ID in order to connect.	3 years ago
hashicorp-copywrite[bot]	d563a3c623	[COMPLIANCE] Add Copyright and License Headers	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