Search (SHIFT+S)
ECS Management API
ECS Object Service API
-
Amazon S3
- S3 Bucket
- S3 Bucket ACL
- S3 Bucket Cors
- S3 Bucket Empty Status Operations
- S3 Bucket Is Stale Allowed
- S3 Bucket Lifecycle
- S3 Bucket List Fanout (Cloud DVR)
- S3 Bucket List Uploads
- S3 Bucket Location
- S3 Bucket Lock Configuration Operations
- S3 Bucket Object Lock Operations
- S3 Bucket Policy
- S3 Bucket Versioning
- S3 Bucket Versions
- S3 Data Node
- S3 Metadata Key List
- S3 Metadata Key System List
- S3 Metadata Search
- S3 Multi Object Delete
- S3 Object
- S3 Object ACL
- S3 Object Detailed Replication Status Operations
- S3 Object Init Uploads
- S3 Object Legal Hold Operations
- S3 Object Replication Info Operations
- S3 Object Retention Operations
- S3 Object Tagging Operations
- S3 Object Uploads
- S3 Options
- S3 Ping
- S3 Retention Update Operation
- S3 Select Operations
- EMC Atmos
- OpenStack Swift
ECS API Changes
Get Profile Mappings for Transformation
GET /object/transformation/{transformationId}/profile/mapping
Returns a list of currently available ProfileMapping entries. The list includes previously manually-set Profile Mappings as well as auto-calculated values.
A ProfileMapping defines a mapping between a pair of data instances defined as a Legacy Storage bucket and Legacy Storage user mapped to a pair of data instances defined as an ECS bucket and an ECS user. ECS needs this mapping to redirect requests to a Legacy Storage bucket using correct Legacy Storage user credentials when some ECS bucket is accessed by an ECS user.
ECS logic, depending on a Legacy Storage type, may offer a set of auto-calculated Profile Mappings. ECS calculates the Profile Mappings based on information about Legacy Storage buckets and users. This simplifies the transformation provision procedure in cases where there are many Legacy Storage buckets and users to be transformed.
Auto-calculated Profile Mappings are less authoritative than manually created ones. If a target_user or target_bucket of an auto-calculated Profile Mapping matches an already existing ECS user or ECS bucket, ECS marks that auto-calculated Profile Mapping as a conflicting one. You cannot start a transformation if conflicting Profile Mappings exist. You can over-ride a conflicting auto-calculated Profile Mapping by setting a manual Profile Mapping entry for a Legacy Storage source profile.
| transformationId | Transformation ID of the transformation. |
Required Roles
Requires one of the following roles:
SYSTEM_ADMIN
SYSTEM_MONITOR
Prerequisites
The following conditions must be met in order to call this operation.
Transformation must exist.
Response Body
Reply contains a list of auto calculated ECS ProfileMappings for each source storage bucket.
| Field | Description | Type | Notes |
| profile_mappings | |||
| mappings |
0-* Elements |
||
| profile_mapping | |||
| source_id | Source ID of transformation mapping | String | |
| target_user | Target user for profile mapping | String | |
| target_bucket | Target bucket for profile mapping | String | |
| target_namespace | Target namespace for profile mapping | String | |
| encryption_enabled | Encryption for target bucket | Boolean | |
| centera_profile | |||
| pool | Centera pool for transformation | String | |
| profile | Centera profile for transformation | String | |
| source_id | Source ID for transformation | String | |
| mask | Mask for transformation | String | |
| s3_profile | |||
| sourceId | Source ID of profile for transformation | String | |
| conflict |
0-* Elements |
||
| conflict_type | profile mappings conflict type | String |