Terraform Provisioner Ansible Versions Save

Ansible with Terraform 0.14.x

v2.1.0

5 years ago

Fixed

New features

  • @adamwg contributed a Dockerfile: https://github.com/radekg/terraform-provisioner-ansible/pull/91, usage documented in the readme
  • new properties added in response to:
    • ansible_ssh_settings.insecure_no_strict_host_key_checking: if true, host key checking will be disabled when connecting to the target host, default false; when connecting via bastion, bastion will not execute any SSH keyscan
    • ansible_ssh_settings.insecure_bastion_no_strict_host_key_checking: if true, host key checking will be disabled when connecting to the bastion host, default false
    • ansible_ssh_settings.user_known_hosts_file: used only when ansible_ssh_settings.insecure_no_strict_host_key_checking=false; if set, the provided path will be used instead of an auto-generate known hosts file; when executing via bastion host, it allows the administrator to provide a known hosts file, no SSH keyscan will be executed on the bastion; default empty string
    • ansible_ssh_settings.bastion_user_known_hosts_file: used only when ansible_ssh_settings.insecure_bastion_no_strict_host_key_checking=false; if set, the provided path will be used instead of an auto-generate known hosts file

Other

v2.0.1

5 years ago

Fixed

v2.0.0

5 years ago

Fixed

  • bastion host support in 1.0.0 was implemented very badly, generally, that version should not be used when bastion host should be used; there are no plans for fixing 1.0.0 bastion support, please switch to 2.x

Breaking changes

  • local provisioning becomes the default, remote provisioning enabled with remote {} resource
  • change plays.playbook and plays.module to a resource
  • remove yes/no strings, boolean values are used instead
  • default values now provided using the defaults resource
  • diff, become and verbose can be set only on plays, no default override for boolean values

New features

Other