v0.5.4

New features:

• Support Nutanix MCS Machine Catalog.

Bugfixes:

• Remove hardcoded minimum functional level in catalog update. #52

Other improvements:

• Add acceptance tests for AWS EC2 machine catalogs.

Full Changelog: v0.5.3...v0.5.4

v0.5.3

New Features:

• Allow setting the Minimum Functional Level for Machine Catalogs and Delivery Groups. #41
• Support for creating and managing Nutanix hypervisor resource pool via Terraform.
• Support VSphere MCS Machine Catalog.
• Support XenServer MCS Machine Catalog.

Breaking change:

• For Machine Catalogs, under provsioning_scheme.machine_config per hypervisor type, the writeback_cache.writeback_cache_memory_size_mb is now a Required field.
• storage and temporary_storage for XenServer hypervisor resource pool is now of type HypervisorStorageModel (previously string).

Bugfixes:

• Fix timeout issue when updating Azure MCS Machine Catalog using machine_profile. #39
• Fix bug when setting multiple pool size schedules. #42
• Fix issue when using Static allocation type for MultiSession Machine Catalogs. Static allocation type is no longer valid for MultiSession Machine Catalogs (only Random allocation type is supported) and appropriate error message will be shown, #44
• Update policy set description to reflect availability. #46
• Fix bug when creating Azure MCS Machine Catalog with identity_type as AzureAD. #47
• Support instance ID and instance name for machine_accounts.machines.machine_name when creating manual provisioning_type power-managed AWS EC2 Machine Catalogs. #48

Other changes:

• service_offering for AWS EC2 now follows AWS EC2 instance type naming convention.

Full Changelog: v0.5.2...v0.5.3

v0.5.2

New Features:

1. Support for creating and managing Vsphere hypervisor resource pool via terraform.
2. Support for creating and managing Site-Admins for CVAD On-Premises customers.
3. Added utility script for detecting config drifting. Please check README for more details.
4. Added utility script for onboarding existing CVAD / DaaS deployment to terraform management by generating terraform TF file that has existing configuration, and import existing resources into terraform state. Please check README for more details.

Bugfixes:
Fixed AWS EC2 MCS machine catalog management. Now you can create and manage MCS machine catalog using AWS EC2 hypervisor and resource pool.
We have also added new example terraform for a full setup for session launch using AWS EC2 MCS provisioning.

Full Changelog: v0.5.1...v0.5.2

v0.5.1

New feature:
Supports enabling Azure AD Device Management in Azure Hypervisor.

Bugfix:
Validator on Delivery Group users list now allows domain that ends with a number

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Breaking change:
Starting from release v0.5.0, all resources will no longer have daas in resource name, i.e. citrix_daas_zone is now citrix_zone. Please refactor your terraform to remove daas from all resource definition.

New features:

1. Support Vsphere / XenServer / Nutanix hypervisor management via terraform
2. Manual Power Managed machine catalog now supports Vsphere / XenServer / Nutanix hypervisor
3. Support managing GPO via terraform
4. Support Hybrid Azure AD (HybridAzureAD) identity type for MCS machine catalogs

Other changes:

1. Repo structure has been streamlined by merging resource and data_source directory
2. Updated README

Full Changelog: v0.4.0...v0.5.0

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

v0.3.6

Breaking change:

• Per ConnectionType hypervisor
• Per ConnectionType hypervisor resource pool

In order to reduce field clutter in documentation, as well as leveraging terraform plugin framework's built-in validation, we decided to separate hypervisor and hypervisor resource pool resource into separate resources based on connection type. This change will eliminate the effort of going through documentation in order to figure out which optional parameter is necessary for the selected connection type.

We are also planning a future change to reduce the complexity of MCS machine catalog resources based on the same idea. It will be available in future update.

New Features:

• Machine catalog Manual provisioning type support
• Machine catalog RemotePC provisioning type support
• Citrix Cloud Gov / Gov Staging environment support #28
• Delivery Group user access restriction support #19 #22

Machine catalog now supports Manual provisioning type besides MCS. While using Manual provisioning type, you can also create RemotePC machine catalog by setting is_remote_pc to true. This change allows on-premises customer who wants to manually provision and manage VDAs to leverage our terraform provider.

Bugfixes / Improvements:

• Fix GCP hypervisor resource pool import when using shared VPC
• Fix a few bugs that could cause provider server to crash
• Added validators to show more explicit error messages in various cases

Refactoring:

• General repository structure refactoring
• Reduced duplicate code
• Go Tests refactoring to avoid test collision while multiple tests are running in parallel

Full Changelog: v0.3.5...v0.3.6

v0.3.5

This release has the following bugfix:

• For Azure, only one of citrix_daas_machine_catalog.provisioning_scheme.machine_config.master_image and citrix_daas_machine_catalog.provisioning_scheme.machine_config.gallery_image will be required. #21

Full Changelog: v0.3.4...v0.3.5

v0.3.4

This release contains the following items:

Breaking change:

• citrix_daas_machine_catalog.provisioning_scheme.machine_config.master_image is now a required property. For GCP catalog, specify the VM or VM snapshot you want to use as the VDA image template for the catalog.

New features:

• Support Azure Gallery Image in machine catalog creation.
• Support shared VPC on GCP in resource pool creation. If you are using shared VPC instead of regular VPC, set citrix_daas_hypervisor_resource_pool.shared_vpc to true.
• Support GCP catalog creation.

Bugfixes and Improvements:

• Implement batch API.
• Fixed issue where certain attributes in citrix_daas_delivery_group resource would show as known after apply every time even without changes.
• Minor bugfixes and improvements

Full Changelog: v0.3.3...v0.3.4

v0.3.3

This release contains the following changes:

• Breaking change:
  count field under citrix_daas_delivery_group.associated_machine_catalogs has been renamed to machine_count for better readability.

• Feature:

1. Support query VDAs associated with either a machine catalog or a delivery group from data source.
2. Feature: Terraform log shows more detailed error messages for different cases of provider initialization failure.

• Bugfix:

1. Added retries in API call to avoid failure from single throttling
2. storage_type field in cirtrix_daas_machine_catalog.provisioning_scheme is now an Optional field. - #16
3. use_managed_disk field in cirtrix_daas_machine_catalog.provisioning_scheme is now an Optional field. - #16
4. Fix issue with bulk creation of resources - #15
5. Support both Azure region name (East US) and Id (eastus)

Full Changelog: v0.3.2...v0.3.3