Class CreateExportDetails

Details for creating the export.

Inheritance

object

CreateExportDetails

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.MemberwiseClone()

object.ReferenceEquals(object, object)

object.ToString()

Namespace: Oci.FilestorageService.Models

Assembly: OCI.DotNetSDK.Filestorage.dll

Syntax

public class CreateExportDetails

Properties

ExportOptions

Declaration

[JsonProperty(PropertyName = "exportOptions")]
public List<ClientOptions> ExportOptions { get; set; }

Property Value

Type Description

Type	Description
List<ClientOptions>	Export options for the new export. For exports of mount targets with IPv4 address, if client options are left unspecified, client options would default to: [ { "source" : "0.0.0.0/0", "requirePrivilegedSourcePort" : false, "access": "READ_WRITE", "identitySquash": "NONE", "anonymousUid": 65534, "anonymousGid": 65534, "isAnonymousAccessAllowed": false, "allowedAuth": ["SYS"] } ] For exports of mount targets with IPv6 address, if client options are left unspecified, client options would be an empty array, i.e. export would not be visible to any clients. Note: Mount targets do not have Internet-routable IP addresses. Therefore they will not be reachable from the Internet, even if an associated `ClientOptions` item has a source of `0.0.0.0/0`. If set to the empty array then the export will not be visible to any clients. The export's `exportOptions` can be changed after creation using the `UpdateExport` operation.

List<ClientOptions>

Export options for the new export. For exports of mount targets with IPv4 address, if client options are left unspecified, client options would default to:
[ { "source" : "0.0.0.0/0", "requirePrivilegedSourcePort" : false, "access": "READ_WRITE", "identitySquash": "NONE", "anonymousUid": 65534, "anonymousGid": 65534, "isAnonymousAccessAllowed": false, "allowedAuth": ["SYS"] } ]
For exports of mount targets with IPv6 address, if client options are left unspecified, client options would be an empty array, i.e. export would not be visible to any clients.
Note: Mount targets do not have Internet-routable IP addresses. Therefore they will not be reachable from the Internet, even if an associated ClientOptions item has a source of 0.0.0.0/0.
If set to the empty array then the export will not be visible to any clients.
The export's exportOptions can be changed after creation using the UpdateExport operation.

ExportSetId

Declaration

[Required(ErrorMessage = "ExportSetId is required.")]
[JsonProperty(PropertyName = "exportSetId")]
public string ExportSetId { get; set; }

Property Value

Type	Description
string	The OCID of this export's export set.

Remarks

Required

FileSystemId

Declaration

[Required(ErrorMessage = "FileSystemId is required.")]
[JsonProperty(PropertyName = "fileSystemId")]
public string FileSystemId { get; set; }

Property Value

Type	Description
string	The OCID of this export's file system.

Remarks

Required

IsIdmapGroupsForSysAuth

Declaration

[JsonProperty(PropertyName = "isIdmapGroupsForSysAuth")]
public bool? IsIdmapGroupsForSysAuth { get; set; }

Property Value

Type	Description
bool?	Whether or not the export should use ID mapping for Unix groups rather than the group list provided within an NFS request's RPC header. When this flag is true the Unix UID from the RPC header is used to retrieve the list of secondary groups from a the ID mapping subsystem. The primary GID is always taken from the RPC header. If ID mapping is not configured, incorrectly configured, unavailable, or cannot be used to determine a list of secondary groups then an empty secondary group list is used for authorization. If the number of groups exceeds the limit of 256 groups, the list retrieved from LDAP is truncated to the first 256 groups read.

Type

Description

bool?

Whether or not the export should use ID mapping for Unix groups rather than the group list provided within an NFS request's RPC header. When this flag is true the Unix UID from the RPC header is used to retrieve the list of secondary groups from a the ID mapping subsystem. The primary GID is always taken from the RPC header. If ID mapping is not configured, incorrectly configured, unavailable, or cannot be used to determine a list of secondary groups then an empty secondary group list is used for authorization. If the number of groups exceeds the limit of 256 groups, the list retrieved from LDAP is truncated to the first 256 groups read.

Locks

Declaration

[JsonProperty(PropertyName = "locks")]
public List<ResourceLock> Locks { get; set; }

Property Value

Type	Description
List<ResourceLock>	Locks associated with this resource.

Path

Declaration

[Required(ErrorMessage = "Path is required.")]
[JsonProperty(PropertyName = "path")]
public string Path { get; set; }

Property Value

Type	Description
string	Path used to access the associated file system. Avoid entering confidential information. Example: /mediafiles

Remarks

Required