azurerm_container_app_environment - Support for Mutual TLS added

[jhisc]

Community Note

• Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
• Please do not leave "+1" or "me too" comments, they generate extra noise for PR followers and do not help prioritize for review

Description

Adding support for Mutual TLS within Azure Container App Environments.
This is a non breaking change and backwards compatable.

Changes can be made to existing resources without requiring a re-creation.
Defaults to false which results in a no-changes to existing infrastructure.

Provider tested to validate:

• New Resources created with MTLS enabled and disabled
• Updating existing resource to Enable/Disable MTLS
• State Refresh where changes made outside of Terraform

Feature enhancement - Not a major chance, optional input
PR looks worse than it is, vast majority of changed files are the new SDK version being pulled into the Vendor folder.

PR Checklist

• I have followed the guidelines in our Contributing Documentation.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
• I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
• I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
  For example: “resource_name_here - description of change e.g. adding property new_property_name_here”

Changes to existing Resource / Data Source

• I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
• I have written new tests for my resource or datasource changes & updated any relevent documentation.
• [] I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
• (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

I have been unable to execute the tests locally, however conducted manual testing with the new provider.

Testing

• My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

• azurerm_container_app_environment - support for the MTLS property [azurerm_container_app_environment - Support for Mutual TLS added #25993]

This is a (please select all that apply):

• Bug Fix
• New Feature (ie adding a service, resource, or data source)
• Enhancement
• Breaking Change

Related Issue(s)

Resolves #21960

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

[katbyte]

Thanks @jhisc 0- overall looks good i just have 1 minor comment i've left inline. Once that is addressed i think this is good to merge provided tests pass

[stephybun]

Thanks for this PR @jhisc! I have two comments/questions on this PR. Would you mind taking a look? Once they're resolved this should be good to go

[jhisc]

Thanks for this PR @jhisc! I have two comments/questions on this PR. Would you mind taking a look? Once they're resolved this should be good to go

Thanks! Both comments have been resolved 👍

[stephybun]

@jhisc nearly there, could you rebase your branch on top of main? That should fix the Vendor dependencies check and then we can run the tests.

[stephybun]

Tests look good, thanks @jhisc LGTM 💯

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.