tf-azurerm-module_primitive-resource_group

Overview

This module is managed via the Launch Terraform skeleton.

Usage

See examples/complete for a full working example.

Module Development

Pre-Requisites

The following commands should be available on your system:

• asdf or mise
• make
• python3 (for pre-commit)

Additionally, your git user and email must be configured. Run the make configure command from the root of the repository to ensure that you meet these requirements.

Pre-Commit hooks

The .pre-commit-config.yaml file defines pre-commit hooks for Terraform formatting, validation, documentation generation, and detect-secrets. Hooks are installed when you run make configure. Go linting runs via make lint in local development and CI, not via pre-commit.

Terratest examples

Post-deploy tests in tests/post_deploy_functional/ and tests/post_deploy_functional_readonly/ target examples/complete via an explicit folder constant in each main_test.go. Adding another example requires a new test entry point or updating that constant; it is not picked up automatically.

Local Validation

You should validate the changes you make to any module locally, prior to pushing your changes in a branch to GitHub.

1. Ensure that you have run make configure successfully.
2. Ensure you are signed into the appropriate cloud provider (e.g. Azure) for the module under test in your current console session.
3. Run the Terraform and Golang linters:

make lint

4. Once linters pass, run integration tests (apply, test, destroy):

make test

The pre-commit validations, as well as the make lint and make test targets, are performed in CI. Running them locally before opening a PR helps ensure a smooth review.

Review & Merge Process

Open a Pull Request to the default (main) branch. The PR title must follow Conventional Commits format to merge and to drive semantic versioning.

Ensure CI workflows pass, address review feedback, and obtain approvals required by CODEOWNERS.

Automatic Updates

Shared configuration and workflow files are largely managed through launch-terraform-skeleton. Avoid one-off edits to copied skeleton files in this repository unless necessary (for example .gitignore entries for generated artifacts). Use copier check-update / copier update when refreshing from the skeleton.

Requirements

Name	Version
terraform	~> 1.0
azurerm	>= 3.77, < 5.0

Modules

No modules.

Resources

Name	Type
azurerm_resource_group.resource_group	resource

Inputs

Name	Description	Type	Default	Required
location	(Required) The Azure Region where the Resource Group should exist. Changing this forces a new Resource Group to be created.	string	n/a	yes
managed_by	(Optional) The ID of the resource that manages this resource group.	string	null	no
name	(Required) The Name which should be used for this Resource Group. Changing this forces a new Resource Group to be created.	string	n/a	yes
tags	(Optional) A mapping of tags which should be assigned to the Resource Group.	map(string)	{}	no

Outputs

Name	Description
id	resource group id
name	resource group name