Adding support for Terraform plan target

[trutled3]

Description

This pull request adds the capability to create a Terraform run using the target option to focus Terraform to specific resources.

Testing plan

Build tfci, go build
export TF_API_TOKEN=<TOKEN>
export TF_CLOUD_ORGANIZATION=<ORG>
Run tfci, tfci -hostname=<HOST> -organization=<ORG> run create -workspace=<WORKSPACE> -target-addr=aws_instance.foo

External links

• Command: plan | Terraform
• tfe golang package: RunCreationOptions

[mjyocca]

@trutled3 Thanks for opening a PR and adding a test case! My team and I will review this today.

[trutled3]

I have updated the PR with your suggestions, thank you again @zainq11 & @mjyocca !

[trutled3]

Great catch @mjyocca . I've made that change and verified on my end. It is ready for your review!

[mjyocca]

Great catch @mjyocca . I've made that change and verified on my end. It is ready for your review!

Awesome thank you for doing that!

Also out of curiosity. What sort of workflows or scenarios from an automation standpoint will this enable for you? (Example for GitHub Actions, dispatch a workflow passing in the target resources etc.)

[trutled3]

Certainly @mjyocca ! That is my mistake for not including that in my PR. The TLDR is that this allows us to target specific resources to update as part of a development lifecycle without affecting other resources in the same Terraform deployment.

I have a few use cases that largely surround have a resource managed with Terraform however updating a specific resource as part of another CI CD process such as building and deploying a new image version to my AWS ECR and then update the resources that leverage this image automatically as part of my CI CD lifecycle. The targeted plan allows for planning changes to just the particular resources instead of planning the entire deployment which may have other working changes that we don't want deployed.

Another use case I have is building and releasing new lambda layer versions, and then updating the associated lambdas to use that newly released lambda layer version by updating the a variable the Terraform deployment uses and having Terraform update the Lambda with that new layer version.

[mjyocca]

Certainly @mjyocca ! That is my mistake for not including that in my PR. The TLDR is that this allows us to target specific resources to update as part of a development lifecycle without affecting other resources in the same Terraform deployment.

I have a few use cases that largely surround have a resource managed with Terraform however updating a specific resource as part of another CI CD process such as building and deploying a new image version to my AWS ECR and then update the resources that leverage this image automatically as part of my CI CD lifecycle. The targeted plan allows for planning changes to just the particular resources instead of planning the entire deployment which may have other working changes that we don't want deployed.

Another use case I have is building and releasing new lambda layer versions, and then updating the associated lambdas to use that newly released lambda layer version by updating the a variable the Terraform deployment uses and having Terraform update the Lambda with that new layer version.

I see thanks for clarifying!

[zainq11]

LGTM

[trutled3]

Thanks @mjyocca and @zainq11 for letting me contribute to this repository!