[AVM Module Issue]: Add option to ignore_change of the the gallery_application

[julienmongin-hcl]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

(Optional) Module Version

No response

(Optional) Correlation Id

No response

Description

Do you think you add an option to ignore the change for the gallery_application

Why : today we have a Azure policy to force the installation of applications via the VM application , so if we rerun the terraform script VM application will be remove

I try to use :

lifecycle {
ignore_changes = [
# Ignore changes to tags, e.g. because a management agent
# updates these based on some ruleset managed elsewhere.
gallery_application,
]
}

But there is no way for the caller of a module to force a new behavior on a resource inside that module...

Thanks
PS : documentation for gallery_applications format is not clear

in the doc

gallery_applications = [
  {
    version_id = "/subscriptions/{subscriptionId}/resourceGroups/<resource group>/providers/Microsoft.Compute/galleries/{gallery name}/applications/{application name}/versions/{version}"
    order      = 1
]

it should be

gallery_applications = [ {version_id = "/subscriptions/{subscriptionId}/resourceGroups/<resource group>/providers/Microsoft.Compute/galleries/{gallery name}/applications/{application name}/versions/{version}", order = 1 } ]

[jchancellor-ms]

@julienmongin-hcl - Thanks for this submission. Let me look and see if there is a way we can improve this. I'll also see if we can clean-up the documentation. I'll look to provide an update next week as we're working on a couple of the feature requests and some bug fixes.

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

Note

This message was posted as per ITA01TF.

[microsoft-github-policy-service]

Caution

**This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days. **

Tip

• To avoid this rule being (re)triggered, the "Needs: Triage 🔍" and "Status: Response Overdue 🚩" labels must be removed when the issue is first responded to!
• Remove the "Needs: Immediate Attention ‼️" label once the issue has been responded to.

Note

This message was posted as per ITA02TF.

[jchancellor-ms]

@julienmongin-hcl - I've released updated documentation and an example in v0.12. This should enable me to test some options for ignoring changes. I'll let you know how it goes.

[jchancellor-ms]

@julienmongin-hcl - Because of the issue documented here, I couldn't find a way to dynamically apply a lifecycle block to this portion of the module.

Additionally, since this section of the API exists in the properties block for the virtual machine, I couldn't move the functionality outside of the module to allow for managing the lifecycle only for the gallery applications configuration. (I attempted this with AzAPI's azapi_update_resource functionality, but it caused the same challenge where the primary vm resource would keep removing the gallery app) Since I have to keep this module generic to accommodate as many standard use cases as possible, setting a static lifecycle configuration to ignore content changes would break functionality for other users.

The only remaining option I can currently recommend if you want to continue using this module's content would be to fork the module and create a dedicated version for your use. (At least until such time that we can work with Hashicorp to prioritize extending the lifecycle block functionality out to a module level.)