Module aws_sdk_fsx::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon FSx can respond with.

Structs

• ActiveDirectoryBackupAttributes

  The Microsoft Active Directory attributes of the Amazon FSx for Windows File Server file system.

• AdministrativeAction

  Describes a specific Amazon FSx administrative action for the current Windows, Lustre, OpenZFS, or ONTAP file system or volume.

• AdministrativeActionFailureDetails

  Provides information about a failed administrative action.

• AggregateConfiguration

  Used to specify configuration options for a volume’s storage aggregate or aggregates.

• Alias

  A DNS alias that is associated with the file system. You can use a DNS alias to access a file system using user-defined DNS names, in addition to the default DNS name that Amazon FSx assigns to the file system. For more information, see DNS aliases in the FSx for Windows File Server User Guide.

• AutoExportPolicy

  Describes a data repository association's automatic export policy. The AutoExportPolicy defines the types of updated objects on the file system that will be automatically exported to the data repository. As you create, modify, or delete files, Amazon FSx for Lustre automatically exports the defined changes asynchronously once your application finishes modifying the file.

• AutoImportPolicy

  Describes the data repository association's automatic import policy. The AutoImportPolicy defines how Amazon FSx keeps your file metadata and directory listings up to date by importing changes to your Amazon FSx for Lustre file system as you modify objects in a linked S3 bucket.

• AutocommitPeriod

  Sets the autocommit period of files in an FSx for ONTAP SnapLock volume, which determines how long the files must remain unmodified before they're automatically transitioned to the write once, read many (WORM) state.

• Backup

  A backup of an Amazon FSx for Windows File Server, Amazon FSx for Lustre file system, Amazon FSx for NetApp ONTAP volume, or Amazon FSx for OpenZFS file system.

• BackupFailureDetails

  If backup creation fails, this structure contains the details of that failure.

• CompletionReport

  Provides a report detailing the data repository task results of the files processed that match the criteria specified in the report Scope parameter. FSx delivers the report to the file system's linked data repository in Amazon S3, using the path specified in the report Path parameter. You can specify whether or not a report gets generated for a task using the Enabled parameter.

• CreateAggregateConfiguration

  Used to specify the configuration options for an FSx for ONTAP volume's storage aggregate or aggregates.

• CreateFileCacheLustreConfiguration

  The Amazon File Cache configuration for the cache that you are creating.

• CreateFileSystemLustreConfiguration

  The Lustre configuration for the file system being created.

• CreateFileSystemOntapConfiguration

  The ONTAP configuration properties of the FSx for ONTAP file system that you are creating.

• CreateFileSystemOpenZfsConfiguration

  The Amazon FSx for OpenZFS configuration properties for the file system that you are creating.

• CreateFileSystemWindowsConfiguration

  The configuration object for the Microsoft Windows file system used in CreateFileSystem and CreateFileSystemFromBackup operations.

• CreateOntapVolumeConfiguration

  Specifies the configuration of the ONTAP volume that you are creating.

• CreateOpenZfsOriginSnapshotConfiguration

  The snapshot configuration to use when creating an Amazon FSx for OpenZFS volume from a snapshot.

• CreateOpenZfsVolumeConfiguration

  Specifies the configuration of the Amazon FSx for OpenZFS volume that you are creating.

• CreateSnaplockConfiguration

  Defines the SnapLock configuration when creating an FSx for ONTAP SnapLock volume.

• CreateSvmActiveDirectoryConfiguration

  The configuration that Amazon FSx uses to join the ONTAP storage virtual machine (SVM) to your self-managed (including on-premises) Microsoft Active Directory directory.

• DataRepositoryAssociation

  The configuration of a data repository association that links an Amazon FSx for Lustre file system to an Amazon S3 bucket or an Amazon File Cache resource to an Amazon S3 bucket or an NFS file system. The data repository association configuration object is returned in the response of the following operations:

• DataRepositoryConfiguration

  The data repository configuration object for Lustre file systems returned in the response of the CreateFileSystem operation.

• DataRepositoryFailureDetails

  Provides detailed information about the data repository if its Lifecycle is set to MISCONFIGURED or FAILED.

• DataRepositoryTask

  A description of the data repository task.

• DataRepositoryTaskFailureDetails

  Provides information about why a data repository task failed. Only populated when the task Lifecycle is set to FAILED.

• DataRepositoryTaskFilter

  (Optional) An array of filter objects you can use to filter the response of data repository tasks you will see in the the response. You can filter the tasks returned in the response by one or more file system IDs, task lifecycles, and by task type. A filter object consists of a filter Name, and one or more Values for the filter.

• DataRepositoryTaskStatus

  Provides the task status showing a running total of the total number of files to be processed, the number successfully processed, and the number of files the task failed to process.

• DeleteFileSystemLustreConfiguration

  The configuration object for the Amazon FSx for Lustre file system being deleted in the DeleteFileSystem operation.

• DeleteFileSystemLustreResponse

  The response object for the Amazon FSx for Lustre file system being deleted in the DeleteFileSystem operation.

• DeleteFileSystemOpenZfsConfiguration

  The configuration object for the Amazon FSx for OpenZFS file system used in the DeleteFileSystem operation.

• DeleteFileSystemOpenZfsResponse

  The response object for the Amazon FSx for OpenZFS file system that's being deleted in the DeleteFileSystem operation.

• DeleteFileSystemWindowsConfiguration

  The configuration object for the Microsoft Windows file system used in the DeleteFileSystem operation.

• DeleteFileSystemWindowsResponse

  The response object for the Microsoft Windows file system used in the DeleteFileSystem operation.

• DeleteVolumeOntapConfiguration

  Use to specify skipping a final backup, adding tags to a final backup, or bypassing the retention period of an FSx for ONTAP SnapLock Enterprise volume when deleting an FSx for ONTAP volume.

• DeleteVolumeOntapResponse

  The response object for the Amazon FSx for NetApp ONTAP volume being deleted in the DeleteVolume operation.

• DeleteVolumeOpenZfsConfiguration

  A value that specifies whether to delete all child volumes and snapshots.

• DiskIopsConfiguration

  The SSD IOPS (input/output operations per second) configuration for an Amazon FSx for NetApp ONTAP, Amazon FSx for Windows File Server, or FSx for OpenZFS file system. By default, Amazon FSx automatically provisions 3 IOPS per GB of storage capacity. You can provision additional IOPS per GB of storage. The configuration consists of the total number of provisioned SSD IOPS and how it is was provisioned, or the mode (by the customer or by Amazon FSx).

• DurationSinceLastAccess

  Defines the minimum amount of time since last access for a file to be eligible for release. Only files that have been exported to S3 and that were last accessed or modified before this point-in-time are eligible to be released from the Amazon FSx for Lustre file system.

• FileCache

  A description of a specific Amazon File Cache resource, which is a response object from the DescribeFileCaches operation.

• FileCacheCreating

  The response object for the Amazon File Cache resource being created in the CreateFileCache operation.

• FileCacheDataRepositoryAssociation

  The configuration for a data repository association (DRA) to be created during the Amazon File Cache resource creation. The DRA links the cache to either an Amazon S3 bucket or prefix, or a Network File System (NFS) data repository that supports the NFSv3 protocol.

• FileCacheFailureDetails

  A structure providing details of any failures that occurred.

• FileCacheLustreConfiguration

  The configuration for the Amazon File Cache resource.

• FileCacheLustreMetadataConfiguration

  The configuration for a Lustre MDT (Metadata Target) storage volume. The metadata on Amazon File Cache is managed by a Lustre Metadata Server (MDS) while the actual metadata is persisted on an MDT.

• FileCacheNfsConfiguration

  The configuration for an NFS data repository association (DRA) created during the creation of the Amazon File Cache resource.

• FileSystem

  A description of a specific Amazon FSx file system.

• FileSystemEndpoint

  An Amazon FSx for NetApp ONTAP file system has two endpoints that are used to access data or to manage the file system using the NetApp ONTAP CLI, REST API, or NetApp SnapMirror. They are the Management and Intercluster endpoints.

• FileSystemEndpoints

  An Amazon FSx for NetApp ONTAP file system has the following endpoints that are used to access data or to manage the file system using the NetApp ONTAP CLI, REST API, or NetApp SnapMirror.

• FileSystemFailureDetails

  A structure providing details of any failures that occurred.

• Filter

  A filter used to restrict the results of describe calls. You can use multiple filters to return results that meet all applied filter requirements.

• LifecycleTransitionReason

  Describes why a resource lifecycle state changed.

• LustreFileSystemConfiguration

  The configuration for the Amazon FSx for Lustre file system.

• LustreLogConfiguration

  The configuration for Lustre logging used to write the enabled logging events for your Amazon FSx for Lustre file system or Amazon File Cache resource to Amazon CloudWatch Logs.

• LustreLogCreateConfiguration

  The Lustre logging configuration used when creating or updating an Amazon FSx for Lustre file system. An Amazon File Cache is created with Lustre logging enabled by default, with a setting of WARN_ERROR for the logging events. which can't be changed.

• LustreRootSquashConfiguration

  The configuration for Lustre root squash used to restrict root-level access from clients that try to access your FSx for Lustre file system as root. Use the RootSquash parameter to enable root squash. To learn more about Lustre root squash, see Lustre root squash.

• NfsDataRepositoryConfiguration

  The configuration for a data repository association that links an Amazon File Cache resource to an NFS data repository.

• OntapFileSystemConfiguration

  Configuration for the FSx for NetApp ONTAP file system.

• OntapVolumeConfiguration

  The configuration of an Amazon FSx for NetApp ONTAP volume.

• OpenZfsClientConfiguration

  Specifies who can mount an OpenZFS file system and the options available while mounting the file system.

• OpenZfsCreateRootVolumeConfiguration

  The configuration of an Amazon FSx for OpenZFS root volume.

• OpenZfsFileSystemConfiguration

  The configuration for the Amazon FSx for OpenZFS file system.

• OpenZfsNfsExport

  The Network File System (NFS) configurations for mounting an Amazon FSx for OpenZFS file system.

• OpenZfsOriginSnapshotConfiguration

  The snapshot configuration used when creating an Amazon FSx for OpenZFS volume from a snapshot.

• OpenZfsUserOrGroupQuota

  Used to configure quotas that define how much storage a user or group can use on an FSx for OpenZFS volume. For more information, see Volume properties in the FSx for OpenZFS User Guide.

• OpenZfsVolumeConfiguration

  The configuration of an Amazon FSx for OpenZFS volume.

• ReleaseConfiguration

  The configuration that specifies a minimum amount of time since last access for an exported file to be eligible for release from an Amazon FSx for Lustre file system. Only files that were last accessed before this point-in-time can be released. For example, if you specify a last accessed time criteria of 9 days, only files that were last accessed 9.00001 or more days ago can be released.

• RetentionPeriod

  Specifies the retention period of an FSx for ONTAP SnapLock volume. After it is set, it can't be changed. Files can't be deleted or modified during the retention period.

• S3DataRepositoryConfiguration

  The configuration for an Amazon S3 data repository linked to an Amazon FSx for Lustre file system with a data repository association. The configuration consists of an AutoImportPolicy that defines which file events on the data repository are automatically imported to the file system and an AutoExportPolicy that defines which file events on the file system are automatically exported to the data repository. File events are when files or directories are added, changed, or deleted on the file system or the data repository.

• SelfManagedActiveDirectoryAttributes

  The configuration of the self-managed Microsoft Active Directory (AD) directory to which the Windows File Server or ONTAP storage virtual machine (SVM) instance is joined.

• SelfManagedActiveDirectoryConfiguration

  The configuration that Amazon FSx uses to join a FSx for Windows File Server file system or an FSx for ONTAP storage virtual machine (SVM) to a self-managed (including on-premises) Microsoft Active Directory (AD) directory. For more information, see Using Amazon FSx for Windows with your self-managed Microsoft Active Directory or Managing FSx for ONTAP SVMs.

• SelfManagedActiveDirectoryConfigurationUpdates

  Specifies changes you are making to the self-managed Microsoft Active Directory (AD) configuration to which an FSx for Windows File Server file system or an FSx for ONTAP SVM is joined.

• SnaplockConfiguration

  Specifies the SnapLock configuration for an FSx for ONTAP SnapLock volume.

• SnaplockRetentionPeriod

  The configuration to set the retention period of an FSx for ONTAP SnapLock volume. The retention period includes default, maximum, and minimum settings. For more information, see Working with the retention period in SnapLock.

• Snapshot

  A snapshot of an Amazon FSx for OpenZFS volume.

• SnapshotFilter

  A filter used to restrict the results of DescribeSnapshots calls. You can use multiple filters to return results that meet all applied filter requirements.

• StorageVirtualMachine

  Describes the Amazon FSx for NetApp ONTAP storage virtual machine (SVM) configuration.

• StorageVirtualMachineFilter

  A filter used to restrict the results of describe calls for Amazon FSx for NetApp ONTAP storage virtual machines (SVMs). You can use multiple filters to return results that meet all applied filter requirements.

• SvmActiveDirectoryConfiguration

  Describes the Microsoft Active Directory (AD) directory configuration to which the FSx for ONTAP storage virtual machine (SVM) is joined. Note that account credentials are not returned in the response payload.

• SvmEndpoint

  An Amazon FSx for NetApp ONTAP storage virtual machine (SVM) has four endpoints that are used to access data or to manage the SVM using the NetApp ONTAP CLI, REST API, or NetApp CloudManager. They are the Iscsi, Management, Nfs, and Smb endpoints.

• SvmEndpoints

  An Amazon FSx for NetApp ONTAP storage virtual machine (SVM) has the following endpoints that are used to access data or to manage the SVM using the NetApp ONTAP CLI, REST API, or NetApp CloudManager.

• Tag

  Specifies a key-value pair for a resource tag.

• TieringPolicy

  Describes the data tiering policy for an ONTAP volume. When enabled, Amazon FSx for ONTAP's intelligent tiering automatically transitions a volume's data between the file system's primary storage and capacity pool storage based on your access patterns.

• UpdateFileCacheLustreConfiguration

  The configuration update for an Amazon File Cache resource.

• UpdateFileSystemLustreConfiguration

  The configuration object for Amazon FSx for Lustre file systems used in the UpdateFileSystem operation.

• UpdateFileSystemOntapConfiguration

  The configuration updates for an Amazon FSx for NetApp ONTAP file system.

• UpdateFileSystemOpenZfsConfiguration

  The configuration updates for an Amazon FSx for OpenZFS file system.

• UpdateFileSystemWindowsConfiguration

  Updates the configuration for an existing Amazon FSx for Windows File Server file system. Amazon FSx only overwrites existing properties with non-null values provided in the request.

• UpdateOntapVolumeConfiguration

  Used to specify changes to the ONTAP configuration for the volume you are updating.

• UpdateOpenZfsVolumeConfiguration

  Used to specify changes to the OpenZFS configuration for the volume that you are updating.

• UpdateSnaplockConfiguration

  Updates the SnapLock configuration for an existing FSx for ONTAP volume.

• UpdateSvmActiveDirectoryConfiguration

  Specifies updates to an FSx for ONTAP storage virtual machine's (SVM) Microsoft Active Directory (AD) configuration. Note that account credentials are not returned in the response payload.

• Volume

  Describes an Amazon FSx volume.

• VolumeFilter

  A filter used to restrict the results of describe calls for Amazon FSx for NetApp ONTAP or Amazon FSx for OpenZFS volumes. You can use multiple filters to return results that meet all applied filter requirements.

• WindowsAuditLogConfiguration

  The configuration that Amazon FSx for Windows File Server uses to audit and log user accesses of files, folders, and file shares on the Amazon FSx for Windows File Server file system. For more information, see File access auditing.

• WindowsAuditLogCreateConfiguration

  The Windows file access auditing configuration used when creating or updating an Amazon FSx for Windows File Server file system.

• WindowsFileSystemConfiguration

  The configuration for this Microsoft Windows file system.

Enums

• ActiveDirectoryErrorType
  When writing a match expression against ActiveDirectoryErrorType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AdministrativeActionType
  When writing a match expression against AdministrativeActionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AliasLifecycle
  When writing a match expression against AliasLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AutoImportPolicyType
  When writing a match expression against AutoImportPolicyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AutocommitPeriodType
  When writing a match expression against AutocommitPeriodType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• BackupLifecycle
  When writing a match expression against BackupLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• BackupType
  When writing a match expression against BackupType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DataCompressionType
  When writing a match expression against DataCompressionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DataRepositoryLifecycle
  When writing a match expression against DataRepositoryLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DataRepositoryTaskFilterName
  When writing a match expression against DataRepositoryTaskFilterName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DataRepositoryTaskLifecycle
  When writing a match expression against DataRepositoryTaskLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DataRepositoryTaskType
  When writing a match expression against DataRepositoryTaskType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DeleteFileSystemOpenZfsOption
  When writing a match expression against DeleteFileSystemOpenZfsOption, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DeleteOpenZfsVolumeOption
  When writing a match expression against DeleteOpenZfsVolumeOption, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DiskIopsConfigurationMode
  When writing a match expression against DiskIopsConfigurationMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DriveCacheType
  When writing a match expression against DriveCacheType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EventType
  When writing a match expression against EventType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FileCacheLifecycle
  When writing a match expression against FileCacheLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FileCacheLustreDeploymentType
  When writing a match expression against FileCacheLustreDeploymentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FileCacheType
  When writing a match expression against FileCacheType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FileSystemLifecycle
  When writing a match expression against FileSystemLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FileSystemMaintenanceOperation
  When writing a match expression against FileSystemMaintenanceOperation, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FileSystemType
  When writing a match expression against FileSystemType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FilterName
  When writing a match expression against FilterName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FlexCacheEndpointType
  When writing a match expression against FlexCacheEndpointType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• InputOntapVolumeType
  When writing a match expression against InputOntapVolumeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LustreAccessAuditLogLevel
  When writing a match expression against LustreAccessAuditLogLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LustreDeploymentType
  When writing a match expression against LustreDeploymentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NfsVersion
  When writing a match expression against NfsVersion, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OntapDeploymentType
  When writing a match expression against OntapDeploymentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OntapVolumeType
  When writing a match expression against OntapVolumeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OpenZfsCopyStrategy
  When writing a match expression against OpenZfsCopyStrategy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OpenZfsDataCompressionType
  When writing a match expression against OpenZfsDataCompressionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OpenZfsDeploymentType
  When writing a match expression against OpenZfsDeploymentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OpenZfsQuotaType
  When writing a match expression against OpenZfsQuotaType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• PrivilegedDelete
  When writing a match expression against PrivilegedDelete, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ReportFormat
  When writing a match expression against ReportFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ReportScope
  When writing a match expression against ReportScope, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceType
  When writing a match expression against ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RestoreOpenZfsVolumeOption
  When writing a match expression against RestoreOpenZfsVolumeOption, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RetentionPeriodType
  When writing a match expression against RetentionPeriodType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SecurityStyle
  When writing a match expression against SecurityStyle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ServiceLimit
  When writing a match expression against ServiceLimit, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SnaplockType
  When writing a match expression against SnaplockType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SnapshotFilterName
  When writing a match expression against SnapshotFilterName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SnapshotLifecycle
  When writing a match expression against SnapshotLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Status
  When writing a match expression against Status, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StorageType
  When writing a match expression against StorageType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StorageVirtualMachineFilterName
  When writing a match expression against StorageVirtualMachineFilterName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StorageVirtualMachineLifecycle
  When writing a match expression against StorageVirtualMachineLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StorageVirtualMachineRootVolumeSecurityStyle
  When writing a match expression against StorageVirtualMachineRootVolumeSecurityStyle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StorageVirtualMachineSubtype
  When writing a match expression against StorageVirtualMachineSubtype, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• TieringPolicyName
  When writing a match expression against TieringPolicyName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Unit
  When writing a match expression against Unit, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• UpdateOpenZfsVolumeOption
  When writing a match expression against UpdateOpenZfsVolumeOption, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• VolumeFilterName
  When writing a match expression against VolumeFilterName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• VolumeLifecycle
  When writing a match expression against VolumeLifecycle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• VolumeStyle
  When writing a match expression against VolumeStyle, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• VolumeType
  When writing a match expression against VolumeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• WindowsAccessAuditLogLevel
  When writing a match expression against WindowsAccessAuditLogLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• WindowsDeploymentType
  When writing a match expression against WindowsDeploymentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.