-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how can i import compute engine metadata from the non-default project? #10961
Comments
…r an update in resource `google_workbench_instance` (hashicorp#10961) [upstream:e69e5f7253af4532e5ed75617a8cab176eef4a72] Signed-off-by: Modular Magician <[email protected]>
…r an update in resource `google_workbench_instance` (#10961) (#18464) [upstream:e69e5f7253af4532e5ed75617a8cab176eef4a72] Signed-off-by: Modular Magician <[email protected]>
This is still an active issue and I beleive it should be classified as a bug instead of a question. #13370 did not fix it. It does not appear to be possible to import this resource when there is no project set at the provider level. In some situations, such as one workspace managing several google cloud projects, setting it at the provider level would be incorrect. |
Given this example: resource "google_compute_project_metadata_item" "test" {
key = "TEST"
value = "FOOBAR"
project = "xxx"
} with a value like commonInstanceMetadata:
fingerprint: 9wSsw7q2AB8=
items:
- key: TEST
value: FOOBAR
kind: compute#metadata Trying to do this:
will of course not work, and the normal import syntax of:
also doesn't seem to work if the provider level configuration has a different project configured, even if |
my code
the docs show that compute engine metadata items can be imported using the key as i tried above, but it seems not to be possible to import a metadata item when the resource belongs to a different project than the provider
i have additionally tried:
is it a bug or is there something im missing?
The text was updated successfully, but these errors were encountered: