-
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
Make google_container_node_pool resources importable. #284
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3def84d
Make google_container_node_pool resources importable.
abogs 933efee
Merge branch 'master' of https://github.com/terraform-providers/terra…
abogs 84aa43f
Merge https://github.com/terraform-providers/terraform-provider-google
drzero42 fa58dee
Add website documentation for importing google_container_node_pool.
drzero42 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
package google | ||
|
||
import ( | ||
"fmt" | ||
"testing" | ||
|
||
"github.com/hashicorp/terraform/helper/acctest" | ||
"github.com/hashicorp/terraform/helper/resource" | ||
) | ||
|
||
func TestAccGoogleContainerNodePool_import(t *testing.T) { | ||
resourceName := "google_container_node_pool.np" | ||
cluster := fmt.Sprintf("tf-nodepool-test-%s", acctest.RandString(10)) | ||
np := fmt.Sprintf("tf-nodepool-test-%s", acctest.RandString(10)) | ||
conf := testAccContainerNodePool_basic(cluster, np) | ||
resource.Test(t, resource.TestCase{ | ||
PreCheck: func() { testAccPreCheck(t) }, | ||
Providers: testAccProviders, | ||
CheckDestroy: testAccCheckContainerNodePoolDestroy, | ||
Steps: []resource.TestStep{ | ||
resource.TestStep{ | ||
Config: conf, | ||
}, | ||
|
||
resource.TestStep{ | ||
ResourceName: resourceName, | ||
ImportState: true, | ||
ImportStateVerify: true, | ||
}, | ||
}, | ||
}) | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hum...
The
Create
method sets the id of the resource to the name of the container node pool.The import will leave the id as zone/cluster/name.
This is not a big deal since we don't use the resource id after creation right now but if we decide to use it in the future, it is nice to have them consistent.
However, only setting the id to name like it's done in
Create
is wrong since it is valid for two node pool across two clusters to have the same name. Currently, we prevent this use case.I created a separate issue (#298) to fix the
Create
method and set the id to zone/cluster/name. This will require a use of schema migration and it is better to do this in a separate PR. Migration will make all the ids consistent.Nothing to do for you here :) I will take care of the other issue.