feat: Set version of promise to TF module version on init in CLI

[catmo-syntasso]

[To discuss]

Context

When initialising a promise via any of the init commands, by default, the version of the promise is set to v0.0.1. We have received feedback from users that when initialising a promise from a Terraform module, they want the version of the Promise to mirror the version of the Terraform Module.

The below is an example command to initialise a promise from a Terraform module:

kratix init tf-module-promise vpc --module-version v5.19.0 --module-source https://github.com/terraform-aws-modules/terraform-aws-vpc.git --group syntasso.io --kind VPC --version v1alpha1 --dir api-confirmation-revisited

The --module-version is a required field so this is information the cli has access to so the suggestion is possible but it may not be what we desire for the design of the init command.

Possible strategies:

• The above, for tf-module promises the promise version matches the version of the module
• The version of the promise is exposed via a --version flag to the init command so users have the option of configuring this when initialising the promise
• The tf-module-promise sub-command has a --match-module-version flag to ensure the promise version matches the module version
• Any more?

[abangser]

Great write up and options. I don't have any other options to add. My vote would be for something like #2 as we already have that in the vanilla init command and that could just be applied to all promise init sub commands.

My second option would be the match-module-version style but with a more generic flag name that could be re-used for any of the generator init commands.

[catmo-syntasso]

I agree with Abby! I have a worry about auto-populating anything like #1 suggests (do I always want the TF module version to be the same as a promise...?)