This repository has been archived by the owner on Jun 12, 2021. It is now read-only.
add null_resource support #122
Merged
Conversation
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
|
Hi @stevestrutt. Thank you for the pull request. It looks complete. Being able to run Ansible via I will run a couple of checks before merging. |
|
Hi Steve, thank you once again for the contribution. I have merged your PR onto an intermediate branch to have the tests status covered. The intermediate PR is now merged to master. I will create a release mid next week, your changes will be in the new version. Happy to hear this is extensively tested on the IBM Cloud! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Added support to allow terraform-provisioner-ansible to be used in local_mode with a null_resource. Target hosts for the provisioner can be specified using
plays.hostsand interpolation from the ip_address of provisioned compute instances, or by passing an inventory file.Included updates to Readme and an additional example.
Using
terraform taint null_resource.xxxxxxxthe provisioner can be triggered to run again on the nextterraform apply.Extensively tested on IBM Cloud. Operation will be the same across all cloud vendors.
Additional comment:
I found when the provisioner is used with a compute resource, it is not necessary to specify a host in the connection block or with plays.hosts. If connection.host is not specified, Terraform passes the public IP address of the instance just created. This usage was not clear in the Readme.