Simplify Service import logic, and allow selecting a version while importing #448
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.
Previously the Service resource import would do a full state refresh twice: once in the
resourceImport
function, and again when Terraform callsresourceRead
again afterwards. This PR simplifies this, to only optionally set thecloned_version
in theresourceImport
function, and delegate the rest of the state refresh to theresourceRead
called by Terraform automatically.If no version is specified for the import, then the Read function will detect
cloned_version
is 0, and select either the active version or latest version. This logic hasn't changed, but theisImport
flag argument is no longer needed.In simplifying the import logic, it seemed like a good opportunity to add a new feature: allowing
@
and a version number to be appended to the ID whilst importing, to enable the user to choose a version. This is optional, and the previous method of only specifying the ID without the version is still supported.