Skip to content

Add project to container cluster import name. #1282

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

Merged
merged 3 commits into from
Apr 3, 2018

Conversation

emilymye
Copy link
Contributor

@emilymye emilymye commented Apr 2, 2018

Fixes #1270

Keeps old format for backwards compat

@emilymye emilymye requested a review from danawillow April 2, 2018 16:18
{
Config: testAccContainerCluster_basic(clusterName),
},
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's actually add this as an additional step to the existing _basic test instead, just to save a bit of time

@emilymye
Copy link
Contributor Author

emilymye commented Apr 3, 2018

Ran test locally:

$ make testacc TEST=./google TESTARGS='-run="TestAccContainerCluster_basic"'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./google -v -run="TestAccContainerCluster_basic" -timeout 120m
=== RUN TestAccContainerCluster_basic
=== PAUSE TestAccContainerCluster_basic
=== CONT TestAccContainerCluster_basic
--- PASS: TestAccContainerCluster_basic (240.77s)
PASS
ok github.com/terraform-providers/terraform-provider-google/google240.932s

@emilymye emilymye force-pushed the container_cluster_import_1270 branch from a616125 to 8174bde Compare April 3, 2018 20:13
@emilymye emilymye merged commit 360260d into hashicorp:master Apr 3, 2018
danawillow pushed a commit that referenced this pull request Jun 14, 2018
## What

As well as #1282 , make `resource_container_node_pool` importer accept `{project}/{zone}/{cluster}/{name}` format to specify the project where the node pool belongs to actually.

## Why

Sometimes I want to import container pool in different project from default SA's. However, currently there is no way to specify project the target node pool belongs to, Terraform tries to retrieve node pool from SA's project, then it fails due to `You cannot import non-existent resources using Terraform import.` error.
@emilymye emilymye deleted the container_cluster_import_1270 branch June 19, 2018 17:48
chrisst pushed a commit to chrisst/magic-modules that referenced this pull request Oct 26, 2018
)

## What

As well as hashicorp/terraform-provider-google#1282 , make `resource_container_node_pool` importer accept `{project}/{zone}/{cluster}/{name}` format to specify the project where the node pool belongs to actually.

## Why

Sometimes I want to import container pool in different project from default SA's. However, currently there is no way to specify project the target node pool belongs to, Terraform tries to retrieve node pool from SA's project, then it fails due to `You cannot import non-existent resources using Terraform import.` error.
chrisst pushed a commit to chrisst/terraform-provider-google that referenced this pull request Nov 9, 2018
* allow import of container cluster by project as well

* update docs for importing container cluster with project

* combine tests
@ghost
Copy link

ghost commented Nov 18, 2018

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Nov 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants