v0.4.0

Breaking change:

citrix_daas_machine_catalog schema has been refactored to have per-hypervisor-connection-type machine_config in provisioning_scheme, i.e. azure_machine_config and gcp_machine_config. This change improves the user experience of creating an MCS machine catalog by consolidating the validators for each hypervisor connection type, and improves the readability of the schema documentation.

New features:

1. Support applications management via citrix_daas_application resource in terraform.
2. Support application folder management via citrix_daas_application_folder resource in terraform.
   Application folder managed outside of terraform can be referenced in terraform via data source citrix_daas_application_folder_details.
3. Support admin scope management via citrix_daas_admin_scope resource.
   Admin scope managed outside of terraform can be reference in terraform via data source citrix_daas_admin_scope.
   For Admin Scopes, support for Tenant Scope in DaaS will be available in future releases. More information about tenant scope can be found here: https://docs.citrix.com/en-us/citrix-daas/manage-deployment/delegated-administration.html#tenant-management
4. Support admin role management via citrix_daas_admin_role resource.
   For Admin Role, the fields can_launch_manage and can_launch_monitor are only supported for Cloud environments. They are not supported for On-Premise environments. More information about Creating and Managing roles can be found here: https://docs.citrix.com/en-us/citrix-daas/manage-deployment/delegated-administration.html#create-and-manage-roles)
5. Delivery group reboot schedule is now configurable via terraform with citrix_daas_delivery_group.reboot_schedule.
6. AzureAD is supported as an option for provisioning_scheme.identity_type for MCS machine catalog creation.
7. Azure MCS machine catalog now supports Azure Machine Profile via provisioning_scheme.azure_machine_config.machine_profile.

Schema change:

When adding users to delivery group, users format has been changed from UPN to SAM name. We also support adding AD groups to delivery groups.

Bugfixes:

1. Fixed an issue where provider will crash when the specified network in network mapping of an MCS machine catalog cannot be found. #31
2. Fixed an issue where machine catalog import did not correctly set the field value for is_remote_pc and is_power_managed.
3. Various bugfixes in schema validation

Improvements:

1. Added go tests to cover GCP MCS machine catalog use case and manual / remotePC machine catalog use case.
2. Minor code improvements.

Full Changelog: v0.3.6...v0.4.0