Skip to content

Subject: Feature Request: Add Registration Token Output to avm/res/desktop-virtualization/host-pool ModuleΒ #5572

Open
@Ngozormor

Description

@Ngozormor

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/desktop-virtualization/host-pool

(Optional) Module Version

No response

Description

Description

When deploying an Azure Virtual Desktop (AVD) host pool using the avm/res/desktop-virtualization/host-pool module, the current implementation does not provide an output for the host pool's registration token. This token is crucial for registering session hosts to the host pool after deployment.

Currently, retrieving the registration token requires using external tools such as Azure PowerShell or Azure CLI after the module deployment has completed. This adds complexity and disrupts automated deployment workflows.

Proposed Solution

I propose adding a new output in the outputs.tf (or equivalent outputs file, depending on the IaC language used, e.g., Bicep or Terraform) of the avm/res/desktop-virtualization/host-pool module. This output should expose the registration token directly, allowing users to easily access it within their IaC pipelines and enabling seamless integration with subsequent deployments (e.g., deploying and joining session hosts).

Justification

This feature would significantly improve the usability and automation capabilities of the module. Providing the registration token as an output aligns with standard AVM practices for exposing necessary resource properties and eliminates the need for manual retrieval steps or dependency on Azure CLI/PowerShell in automated deployments. I have implemented this feature in a fork of the repository and believe it addresses a common need within the community.

(Optional) Correlation Id

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions