Skip to content

v0.4 bug fixes#72

Merged
jchancellor-ms merged 1 commit intomainfrom
v0.4.0-bug-fixes
Feb 5, 2026
Merged

v0.4 bug fixes#72
jchancellor-ms merged 1 commit intomainfrom
v0.4.0-bug-fixes

Conversation

@jchancellor-ms
Copy link
Contributor

@jchancellor-ms jchancellor-ms commented Feb 4, 2026

Description

Corrects Foundry naming and firewall policy linking issues.

Fixes #29

Type of Change

  • Non-module change (e.g. CI/CD, documentation, etc.)
  • Azure Verified Module updates:
    • Bugfix containing backwards compatible bug fixes
      • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
      • The bug was found by the module author, and no one has opened an issue to report it yet.
    • Feature update backwards compatible feature updates.
    • Breaking changes.
    • Update to documentation

Checklist

  • I'm sure there are no other open Pull Requests for the same update/change
  • My corresponding pipelines / checks run clean and green without any errors or warnings
  • I did run all pre-commit checks

@microsoft-github-policy-service

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the Terraform Issue Triage documentation.

@jchancellor-ms
Copy link
Contributor Author

Publishing this even though the cosmos PE's timed out during destroy. This is intermittent and will need to be corrected in the cosmos resource module.

@jchancellor-ms jchancellor-ms merged commit 90eb74f into main Feb 5, 2026
13 of 15 checks passed
@jchancellor-ms jchancellor-ms deleted the v0.4.0-bug-fixes branch February 5, 2026 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs: Triage 🔍 Maintainers need to triage still

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[AVM Module Issue]: Azure Firewall Policy is not associated with the Firewall instance deployed

1 participant