[Feature]: Support multiple major versions

[zioproto]

Module Name

terraform-azurerm-aks

Description

Currently the pipeline only supports testing changes against the main branch.

In AKS now we have a release 6.8.0 and a 7.0.0 release. Because upgrading to 7.0.0 is a breaking change, some customers are holding on 6.8.0 until they have time to test the breaking changes.

Now we merged a bug fix in main:
Azure/terraform-azurerm-aks#369

This fix will be shipped to folks using 7.1.0, but we don't have the tooling to deliver the fix for a 6.8.1 release where we cherry-pick that specific fix.

Example usage

No response

Other information

No response

[lonegunmanb]

Supporting multiple major versions could solve our user's issue while avoid potential breaking changes, but it would make our CI pipeline more complex. Our CI pipeline is designed for a single main branch workflow, multiple major versions require multiple actively maintained branches.

[lonegunmanb]

To support concurrent development for multiple major versions in a module’s repo is very difficult, but a new idea just comes in: we can fork the module repo to a new repo, let’s say terraform-azurerm-aks module, we just released v7.0.0 and the previous version is v6.8.0. We can create a new repo named terraform-azurerm-aks-v6, and release v6.8.1 there. All our customers need to do is change the module’s source and version in their code, run terraform init, and that’s all. WDYT?