[FEATURE] Improve clone with after action

[abtris]

Is your feature request related to a problem? Please describe.

I'm using clone feature to create new regions. Region is main stack in our structure. If I need create new region I can just terramate experimental clone eastus eastus2 and have new region. But what I'm missing that after that I need change location in config file in stack I called region_config.tm.hcl and run terramate generate to update all tree.

Describe the solution you'd like

Will be great if I can script it via scripts and just add as after action for clone. If we can have accessible name of cloned stack that we can use as variable that will great.

Describe alternatives you've considered
Maybe is some other way how to do it but I don't find any.

Additional context
region_config.tm.hcl contains for variables for specific for Azure cloud as (location, subscriptionId, environment).

[mariux]

Thanks for sharing this idea. clone is meant to be used in shell scripts or on command line. So any action you want to do after the clone command can be added to the shell script or needs to be executed afterwards (This assumes you have the script you want to execute after anyways)

You can execute actions just on the changed stacks to limit it to the newly cloned stack.

You could also extract the region/location based on the path and do not need to hard code it.

If this doe snot help, we would need to understand your context better. Please share additional information here.