Struct aws_sdk_fsx::types::FileCacheDataRepositoryAssociation

#[non_exhaustive]
pub struct FileCacheDataRepositoryAssociation {
    pub file_cache_path: Option<String>,
    pub data_repository_path: Option<String>,
    pub data_repository_subdirectories: Option<Vec<String>>,
    pub nfs: Option<FileCacheNfsConfiguration>,
}

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.

The DRA does not support automatic import or automatic export.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

file_cache_path: Option<String>

A path on the cache that points to a high-level directory (such as /ns1/) or subdirectory (such as /ns1/subdir/) that will be mapped 1-1 with DataRepositoryPath. The leading forward slash in the name is required. Two data repository associations cannot have overlapping cache paths. For example, if a data repository is associated with cache path /ns1/, then you cannot link another data repository with cache path /ns1/ns2.

This path specifies where in your cache files will be exported from. This cache directory can be linked to only one data repository, and no data repository other can be linked to the directory.

The cache path can only be set to root (/) on an NFS DRA when DataRepositorySubdirectories is specified. If you specify root (/) as the cache path, you can create only one DRA on the cache.

The cache path cannot be set to root (/) for an S3 DRA.

data_repository_path: Option<String>

The path to the S3 or NFS data repository that links to the cache. You must provide one of the following paths:

• The path can be an NFS data repository that links to the cache. The path can be in one of two formats:

  • If you are not using the DataRepositorySubdirectories parameter, the path is to an NFS Export directory (or one of its subdirectories) in the format nsf://nfs-domain-name/exportpath. You can therefore link a single NFS Export to a single data repository association.

  • If you are using the DataRepositorySubdirectories parameter, the path is the domain name of the NFS file system in the format nfs://filer-domain-name, which indicates the root of the subdirectories specified with the DataRepositorySubdirectories parameter.

• The path can be an S3 bucket or prefix in the format s3://myBucket/myPrefix/.

data_repository_subdirectories: Option<Vec<String>>

A list of NFS Exports that will be linked with this data repository association. The Export paths are in the format /exportpath1. To use this parameter, you must configure DataRepositoryPath as the domain name of the NFS file system. The NFS file system domain name in effect is the root of the subdirectories. Note that DataRepositorySubdirectories is not supported for S3 data repositories.

nfs: Option<FileCacheNfsConfiguration>

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

Implementations

impl FileCacheDataRepositoryAssociation

pub fn file_cache_path(&self) -> Option<&str>

A path on the cache that points to a high-level directory (such as /ns1/) or subdirectory (such as /ns1/subdir/) that will be mapped 1-1 with DataRepositoryPath. The leading forward slash in the name is required. Two data repository associations cannot have overlapping cache paths. For example, if a data repository is associated with cache path /ns1/, then you cannot link another data repository with cache path /ns1/ns2.

This path specifies where in your cache files will be exported from. This cache directory can be linked to only one data repository, and no data repository other can be linked to the directory.

The cache path can only be set to root (/) on an NFS DRA when DataRepositorySubdirectories is specified. If you specify root (/) as the cache path, you can create only one DRA on the cache.

The cache path cannot be set to root (/) for an S3 DRA.

pub fn data_repository_path(&self) -> Option<&str>

The path to the S3 or NFS data repository that links to the cache. You must provide one of the following paths:

• The path can be an NFS data repository that links to the cache. The path can be in one of two formats:

  • If you are not using the DataRepositorySubdirectories parameter, the path is to an NFS Export directory (or one of its subdirectories) in the format nsf://nfs-domain-name/exportpath. You can therefore link a single NFS Export to a single data repository association.

  • If you are using the DataRepositorySubdirectories parameter, the path is the domain name of the NFS file system in the format nfs://filer-domain-name, which indicates the root of the subdirectories specified with the DataRepositorySubdirectories parameter.

• The path can be an S3 bucket or prefix in the format s3://myBucket/myPrefix/.

pub fn data_repository_subdirectories(&self) -> &[String]

A list of NFS Exports that will be linked with this data repository association. The Export paths are in the format /exportpath1. To use this parameter, you must configure DataRepositoryPath as the domain name of the NFS file system. The NFS file system domain name in effect is the root of the subdirectories. Note that DataRepositorySubdirectories is not supported for S3 data repositories.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .data_repository_subdirectories.is_none().

pub fn nfs(&self) -> Option<&FileCacheNfsConfiguration>

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

impl FileCacheDataRepositoryAssociation

pub fn builder() -> FileCacheDataRepositoryAssociationBuilder

Creates a new builder-style object to manufacture FileCacheDataRepositoryAssociation.

Trait Implementations

impl Clone for FileCacheDataRepositoryAssociation

fn clone(&self) -> FileCacheDataRepositoryAssociation

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for FileCacheDataRepositoryAssociation

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for FileCacheDataRepositoryAssociation

fn eq(&self, other: &FileCacheDataRepositoryAssociation) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for FileCacheDataRepositoryAssociation