Questions: - How will the user specify where the statefile is? Is this config for the plugin or part of the lookup? - How will the user specify the name of the target? - How will the user specify connection info(host)? - Is there anything we can do that is terraform specific?
Always unconditionally print a warning to manually verify Puppet code as a comment at top of the plan
Run puppet plan through parser and validator and error if it's invalid (exit nonzero but still print plan)
Questions: - How will the user specify where the statefile is? Is this config for the plugin or part of the lookup? - How will the user specify the name of the target?
- How will the user specify connection info(host)? Plugin configuration?
- Is there anything we can do that is terraform specific?
Always unconditionally printAt least try shelling out to `tf state` - if it's not available fail. State server on it's own is not supported. Need to have the terraform project directory path, and a warning second optional path to manually verify Puppet code the statefile itself if you have multiple. Should be passed as a comment at top parameter to the lookup, as opposed to a way of configuring the plan lookup
Run puppet plan through parser and validator and error if it's invalid (exit nonzero but still print plan)
Questions: - How will the user specify where the statefile is? Is this config for the plugin or part of the lookup? - How will the user specify the name of the target? - How will the user specify connection info(host)? Plugin configuration? - Is there anything we can do that is terraform specific?
At least try shelling out to `tf state` - if it's not available fail. State server on it's own is not supported.
Need to have the terraform project directory path, and a second optional path to the statefile itself if you have multiple. Should be passed as a parameter to the lookup, as opposed to a way of configuring the lookup
So you specify a resource_type which is the "scope" in terraform where your resource exists, specified in the terraform-dot-syntax. Below that you specify bolt config, where each config option accepts a terraform-dot-syntax scope for looking up fields in the top level syntax. Ideally this will also accept regexes.
Questions: - How will the user specify where the statefile is? A path to the terraform project, with an optional subpath key to the specific file - Is this config for the plugin or part of the lookup? Part of the lookup
- How will the user specify the name of the target? - How will the user specify connection info(host)? Plugin configuration? - Is there anything we can do that is terraform specific?
At least try shelling out to `tf state` - if it's not available fail. State server on it's own is not supported.
Need to have the terraform project directory path, and a second optional path to the statefile itself if you have multiple. Should be passed as a parameter to the lookup, as opposed to a way of configuring the lookup
So you specify a resource_type which is the "scope" in terraform where your resource exists, specified in the terraform-dot-syntax. Below that you specify bolt config, where each config option accepts a terraform-dot-syntax scope for looking up fields in the top level syntax. Ideally this will also accept regexes.
A new plugin was added to inventory v2 that can load terraform state and map resource properties to target parameters. This allows a terraform project to be used to dynamically determine the targets to use when running Bolt.