You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
In the other Terraform providers we can add in the universe_domain and custom_<service>_endpoint fields to specify other uris for the API endpoints and entire other sets of infrastructure. Packer's endpoints seem to be hard coded, and I would like to see this exposed to the user.
Use Case(s)
Users of GCP Trusted partner clouds (TPCs) may want to build images using packer, but they would not be able to because they would be in a different universe.
Additionally this would be useful for internal testing where we use different endpoints for APIs that haven't become available yet.
The text was updated successfully, but these errors were encountered:
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
In the other Terraform providers we can add in the
universe_domain
andcustom_<service>_endpoint
fields to specify other uris for the API endpoints and entire other sets of infrastructure. Packer's endpoints seem to be hard coded, and I would like to see this exposed to the user.Use Case(s)
Users of GCP Trusted partner clouds (TPCs) may want to build images using packer, but they would not be able to because they would be in a different universe.
Additionally this would be useful for internal testing where we use different endpoints for APIs that haven't become available yet.
The text was updated successfully, but these errors were encountered: