doc: make sure the doc clearly states which ID should be passed on importing. #86
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.
What kind of change does this PR introduce?
This is a simple documentation update.
What is the current behavior?
At the moment, we already have a live project running and would like to import its configuration into Terraform management.
The problem we ran into the first time was that we used the wrong project id and Terraform still told us "Import successful!", which led to a problem later when we ran
terraform plan
. This change makes sure we tell users what should be run on the import step, since importing existing projects is a pretty common use case.edited: we found that the code snippets under
examples/
had it explained better, but guess no harm to make the doc more clear? 😄