Skip to content

[AVM Module Issue]: Support for Application Gateway Backend Pool placement in different subscription #242

@konopkap

Description

@konopkap

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

(Optional) Module Version

0.20.0

(Optional) Correlation Id

No response

Description

Currently adding VM to Application Gateway Backend Pool is supported via network_interfaces.[].ip_configurations.[].app_gateway_backend_pools.[].app_gateway_backend_pool_resource_id variable. However it works only if both VM and Application Gateway are in the same subscription (effectively using the same Terraform provider).

It's common scenario to have Application Gateway in separate subscription than VMs are deployed to - hence it would be useful to support that as well (exposing possibility to pass different provider for Backend Pool configuration).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions