Options
All
  • Public
  • Public/Protected
  • All
Menu

Namespace CreateExportDetails

Details for creating the export.

Properties

Optional exportOptions

exportOptions: Array<ClientOptions>

Export options for the new export. If left unspecified, defaults to:

[ { \"source\" : \"0.0.0.0/0\", \"requirePrivilegedSourcePort\" : false, \"access\": \"READ_WRITE\", \"identitySquash\": \"NONE\", \"anonymousUid\": 65534, \"anonymousGid\": 65534, \"isAnonymousAccessAllowed\": false, \"allowedAuth\": [\"SYS\"] } ]

*Note:** Mount targets do not have Internet-routable IP addresses. Therefore they will not be reachable from the Internet, even if an associated {@code ClientOptions} item has a source of {@code 0.0.0.0/0}.

*If set to the empty array then the export will not be visible to any clients.**

The export's {@code exportOptions} can be changed after creation using the {@code UpdateExport} operation.

exportSetId

exportSetId: string

The OCID of this export's export set.

fileSystemId

fileSystemId: string

The OCID of this export's file system.

Optional isIdmapGroupsForSysAuth

isIdmapGroupsForSysAuth: undefined | false | true

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.

path

path: string

Path used to access the associated file system.

Avoid entering confidential information.

Example: {@code /mediafiles}

Functions

getDeserializedJsonObj

getJsonObj