seperate "rover" logic to allow custom container environments?

It seems 99% of the rover container is pretty standard fare, and that most the "magic" is the rover bash which has a clever way of determining the appropriate tfstate location in a standard way.

I have a few clients who love this model of approach, but would like to use custom dev containers with extra tools like packer/ansible (yes it makes things bigger, but standardizing for gitops is worth it). Are the plans to offer this wrapper seperatelly? Would be a huge win in terms of flexibility. Basically thinking of something like terragrunt: extra binary that depends on TF making it ultra portable.

Start by reading the rover container and rover bash logic described in the issue, focusing on how the Terraform state location is determined. Define the boundary between the reusable wrapper and the container before assessing how custom dev containers with tools such as packer or ansible would use it; done means the approach is specified well enough to implement and document.

Written by the indexing model from the issue text.