I've update the AWS , Docker , Kubernetes TF code to work on latests version of Boundary including the updated TF provider with hosts sources instead of host sets on targets.
I also added a facilitator to get the correct boundary version on the AWS documentation.
as well as added tf outputs on all code to facilitate getting started with boundary after a succesfull TF run.
as well as a "destroy-tf-run" helped to ease clean up of resources. (without it the resources get destroyed before boundary resources and a destroy run fails)
I've update the AWS , Docker , Kubernetes TF code to work on latests version of Boundary including the updated TF provider with hosts sources instead of host sets on targets.
I also added a facilitator to get the correct boundary version on the AWS documentation.
as well as added tf outputs on all code to facilitate getting started with boundary after a succesfull TF run.
as well as a "destroy-tf-run" helped to ease clean up of resources. (without it the resources get destroyed before boundary resources and a destroy run fails)