Profile Microservices
Use the CDAP Profile Microservices to create profiles, list available profiles, and retrieve information about profiles
All methods or endpoints described in this API have a base URL (typically http://<host>:11015
 or https://<host>:10443
) that precedes the resource identifier, as described in the Microservices Conventions. These methods return a status code, as listed in the Microservices Status Codes.
Write a Profile
A system profile can be created or updated with an HTTP PUT method to the URL:
PUT /v3/profiles/<profile-name>
A user profile can be created or updated with an HTTP PUT method to the URL:
PUT /v3/namespaces/<namespace-id>/profiles/<profile-name>
The request body must be a JSON object that specifies the profile details.
$ PUT /v3/namespace/default/profiles/dataproc -d
{
"label": "Dataproc",
"description": "My Dataproc profile",
"provisioner": {
"name": "gcp-dataproc",
"properties": [
{
"name": "projectId",
"value": "my project id",
"isEditable": false
},
...
]
}
}
List Profiles
To list all system profiles, submit an HTTP GET request:
To list all user profiles, submit an HTTP GET request:
This will return a JSON array that lists each profile. For the user profiles endpoint, if the includeSystem query param is set to true, all system profiles will also be returned in the response.
Retrieve Profile Details
To retrieve details about a system profile, submit an HTTP GET request:
To retrieve details about a user profile, submit an HTTP GET request:
This will return a JSON object that contains details about the profile.
Disable Profile
To disable a system profile, submit an HTTP POST request:
To disable a user profile, submit an HTTP POST request:
Enable Profile
To enable a system profile, submit an HTTP POST request:
To enable a user profile, submit an HTTP POST request:
Delete Profile
To delete a system profile, submit an HTTP DELETE request:
To delete a user profile, submit an HTTP POST request:
In order to delete a profile, the profile must be disabled, it must not be assigned to any entity, and it must not be in use by any active program runs. If any of these conditions is not met, a 409 will be returned.
Created in 2020 by Google Inc.