HCL good first issues

The upstream CNI version 1.22.1 requires additional IAM permissions for subnet discovery, which are not currently included in the Terraform module. This can cause the CNI to fail on startup. The issue suggests adding two specific IAM permissions to the `node_groups.tf` file to resolve this.

The user is reporting a deadlock when using `terragrunt-atlantis-config generate` with a circular dependency between two Terragrunt modules. The issue appears to stem from the function call suppression mechanism, which hangs indefinitely when encountering this circular dependency. The user suggests implementing deadlock or circular dependency detection to provide a clear error message.

The coder-server extension needs to reliably install extensions even when the project folder hasn't been fully checked out yet. The current auto-install mechanism fails in this scenario, and a workaround involves polling for the directory's existence before proceeding with the installation.

This issue addresses outdated documentation for testing frameworks. The `testing-validation.md` file incorrectly references Terratest and `go test` examples, while the actual implementation uses native `terraform test` with `.tftest.hcl` files. The goal is to update the documentation to accurately reflect the current testing approach, including examples of native Terraform tests and correct information for JavaScript and Rust testing.

The user is seeking guidance on migrating their existing infrastructure from the deprecated `terraform-azurerm-openai` module to the recommended new module. They want to understand the process without having to completely re-provision their resources.

This is a feature request to add an example for diagnostic settings within an AVM module. The user has confirmed no prior issues exist and has labeled it as a 'help wanted' feature request for Terraform.

This issue requests the implementation of a Gatekeeper policy to prevent the creation of any resources within the default Kubernetes namespace. The goal is to avoid orphaned resources that are difficult to track and manage, improving platform hygiene.

This issue requests the addition of a new topic on Backstage, a developer portal framework, to the "devops-basics" repository. The topic should follow an established structure, including a README, basic examples, and practice exercises, and is considered a high priority for the Platform Engineering learning path.

This issue proposes adding a new topic about Pulumi, an Infrastructure as Code tool, to the devops-basics repository. The goal is to create a comprehensive Pulumi section that includes a README, a basic runnable example, and practice exercises, complementing the existing Terraform content. This addition is marked as a medium priority and is suitable for new contributors.

This issue requests the addition of a new topic on Dagger, a CI/CD tool, to the devops-basics repository. The contribution should follow an existing topic structure, including a README, basic examples, and practice exercises. This enhancement is prioritized as medium due to Dagger's growing popularity as a code-first CI/CD alternative.

This issue requests the addition of a new topic on Crossplane to the devops-basics repository. The topic should cover what Crossplane is, its prerequisites, installation, basic usage, and advanced concepts, including a runnable example and practice exercises. This is a high-priority enhancement aligned with the repository's focus on platform engineering.

This issue requests the addition of a new topic on FluxCD, a GitOps tool for Kubernetes, to the devops-basics repository. The new topic should follow an established structure, including a README, a runnable basic example, and practice exercises, aligning with the repository's existing content and roadmap priorities.

This issue is a call for users to share their experiences with Terra, a project. Contributors are encouraged to briefly describe how they, their projects, or companies utilize Terra, with specific interest in distributions, other open-source projects, and workplace usage. The goal is to gather community feedback and identify adoption patterns.

The terraform-aws-eventbridge module incorrectly configures IAM permissions for EventBridge Pipes targeting Firehose. It only allows `firehose:PutRecord`, but when batching is enabled for SQS sources, EventBridge Pipes attempts to use `firehose:PutRecordBatch`, leading to an AccessDenied error. The module lacks a direct way to add custom IAM policies to the pipe's execution role to grant this necessary permission.

This issue proposes making the host recovery watcher an optional feature. Currently, it's installed by default when host orchestration is enabled, preventing users from disabling it while keeping certain host network configurations. The proposed change adds a configurable option to disable the watcher, ensuring existing deployments are unaffected by default.

This issue proposes to improve input validation for VLAN tags within a VNet module. Currently, invalid VLAN IDs (like 0, 4095, or non-integers) are accepted by the module and only fail later in the deployment process. The proposed change is to reject these invalid values upfront with a clear module error, ensuring only valid VLAN tags from 1 to 4094 are processed.

This issue proposes migrating deprecated Proxmox SDN resource names within a Terraform module to their newer, supported equivalents. The goal is to ensure compatibility with upcoming Proxmox provider versions and prevent deployment disruptions by implementing a state-safe upgrade path for existing SDN objects. The change involves updating module references, tests, and documentation, while also ensuring validation passes and deprecation warnings are resolved.

This issue proposes adding regression tests for the `ipam_prefixes` output contract. The goal is to ensure that changes to this output do not break downstream integrations by asserting its structure, DHCP values, and metadata. The tests should be independent of a live Proxmox endpoint and cover various DHCP configurations and ordering scenarios.

This issue proposes to add validation to prevent the use of SNAT when host L3 networking is disabled, as SNAT is internally disabled in this configuration and the plan currently fails to inform the user. The change involves adding input validation or a lifecycle precondition to reject this invalid combination and includes adding specific module tests to cover valid and invalid scenarios.

This issue proposes to improve the documentation by adding instructions on how to run local Terraform module tests. Currently, the CONTRIBUTING.md and README.md only mention formatting and validation, not the `terraform test` command that is now used in CI. The goal is to make it easier for contributors to run these tests locally before submitting pull requests.

This bug report indicates that the AWS Systems Manager (SSM) parameter paths for Windows Server 2022 Core and Full AMIs are incorrectly swapped within the EKS managed node group module. This means that when users attempt to deploy a Core AMI, they will receive the Full AMI, and vice-versa, leading to unexpected deployments.

This issue aims to simplify and standardize the MegaLinter workflow in the repository by adopting the public NaNLABS baseline. The goal is to make the workflow more understandable and maintainable for contributors while ensuring essential features like diff-only validation for pull requests and artifact reporting are preserved.

This issue requests updating Danger, a CI tool, to enforce a new standard pull request template. Danger should warn users if required sections like 'Summary', 'Type of change', 'How was this tested?', and 'Checklist' are missing, while maintaining existing checks for issue references and exemptions for automated PRs.