feat!: introduce basic Terratest based tests, unified Makefile and ChatOPS like workflows

[FoSix]

Description

This PR will introduce:

• a single Makefile, repository-wide, flexible enough to handle any new Terratest based test.
• Terratest based action (in place of the old plan/apply, Terraform based one)
• ChatOPS workflows.

Motivation and Context

Makefile

With a single Makefile there will be no copy pasting between modules. The current one is capable of running any test in any module (modules/examples).

TL;DR
To run a test (from the repository's root folder):

make [module path] ACTION=[test to run]

Example:

make examples/common_vmseries ACTION=Apply

Run make help for more details.

Terratest based action

This action is simply a GH Actions wrapper around the new Makefile. It will be fully usable by the reusable workflows introduced in this PR.

ChatOPS introduction

The ChatOPS-like workflows provide a way of running on demand, Terratest based tests. They can become handy in situations where a particular test is not run in PR CI workflow (Apply/Idempotence), or the CI workflow is not triggered (PRs created by other workflows, like pre-commit dependencies update).

Currently there are 4 supported commands:

• sca - runs pre-commit with all tests
• plan - runs plan action
• apply - runs apply action
• idempotence - runs idempotence test (apply following a plan)

The 1^st one takes no parameters. The remaining can take two:

• paths - space separated list of module paths to test
• tf_version - (optional) space separated list of Terraform versions to use to run the test, when skipped, the latest Terraform version will be used.

Example:

/validate paths="examples/common_vmseries modules/vnet"

load_balancer module

There is a small change in this module to add flexibility to how we specify the NSG. Next to the old approach one can also use key values from the VNET definition to reference an NSG that will be created by the Terraform code.

How Has This Been Tested?

Some of the tests can be seen in the PR CI triggered by this workflow.
The ChatOPS tests can be run/tested on the Azure test repo.

Screenshots (if appropriate)

Types of changes

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes if appropriate.
• All new and existing tests passed.

[sebastianczech]

👍

[sebastianczech]

Great work 👍