Asynchronously creates a Git folder and clones the repository

post

/20260430/aiDataPlatforms/{aiDataPlatformId}/workspaces/{workspaceKey}/gitFolders

Asynchronously creates a Git folder and clones the repository. The aidp-async-operation-key header identifies the operation. Once SUCCEEDED, the folder's HEAD response with shouldIncludeMetadata=true exposes system:repoKey in the JSON file-metadata header for subsequent Git APIs.

Request

Path Parameters
Header Parameters
  • Maximum Length: 1000
    For optimistic concurrency control. In the PUT or DELETE call for a resource, set the `if-match` parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value.
  • Maximum Length: 255
    Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
  • Maximum Length: 64
    A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of running that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and removed from the system, then a retry of the original creation request might be rejected.
Body ()
The information to be updated.
Root Schema : CreateGitFolderDetails
Type: object
The data to create a Git folder in a workspace.
Show Source
  • Minimum Length: 1
    Maximum Length: 400
    Git branch name that is cloned.
  • Minimum Length: 1
    Maximum Length: 255
    Key of the current user's GIT_ACCOUNT user setting for repository authentication. User setting listings identify it by settingType=GIT_ACCOUNT and displayName; the matching entry's key is the credentialKey.
  • Minimum Length: 1
    Maximum Length: 255
    Key of the credential containing the Git server's TLS CA certificate, returned by credential listings filtered by displayName. Required when isPrivateConnectivityEnabled is true.
  • Minimum Length: 0
    Maximum Length: 1000
    Short description about the git repository.
  • Minimum Length: 1
    Maximum Length: 1000
    Workspace-relative path of the Git folder, without a leading slash (for example, `sample-repo`). The folder is located at `/Workspace/`.
  • Minimum Length: 1
    Maximum Length: 200
    Key of the private network profile used for Git connectivity, returned by private network profile listings filtered by name. Required when isPrivateConnectivityEnabled is true.
  • Maximum Length: 200
    Default Value: GIT
    key corresponding to Git service provider in git provider table.
  • Minimum Length: 1
    Maximum Length: 1000
    Git repository url used to clone.
  • Default Value: false
    Whether this Git folder uses private network connectivity.
  • SparseCheckoutDetails
    Sparse checkout configuration for a git repository. Only cone mode is supported. Specify only when creating a sparse git folder; sparse checkout cannot be enabled later for a non-sparse git folder. For sparse git folders, settings updates can change cone folder patterns but cannot enable or disable sparse checkout.
Nested Schema : SparseCheckoutDetails
Type: object
Sparse checkout configuration for a git repository. Only cone mode is supported. Specify only when creating a sparse git folder; sparse checkout cannot be enabled later for a non-sparse git folder. For sparse git folders, settings updates can change cone folder patterns but cannot enable or disable sparse checkout.
Show Source
  • Default Value: CONE
    Allowed Values: [ "CONE" ]
    Sparse checkout matching mode. Git supports cone and non-cone sparse checkout pattern styles; AIDP supports cone mode only.
  • patterns
    Minimum Number of Items: 0
    Maximum Number of Items: 100
    Repository-root-relative folder paths to include in the sparse worktree. Cone patterns apply only to folders; root-level files in the repository are always materialized. Empty or omitted patterns materialize root-level files only.
Nested Schema : patterns
Type: array
Minimum Number of Items: 0
Maximum Number of Items: 100
Repository-root-relative folder paths to include in the sparse worktree. Cone patterns apply only to folders; root-level files in the repository are always materialized. Empty or omitted patterns materialize root-level files only.
Show Source
Back to Top

Response

Supported Media Types

200 Response

Git folder creation was accepted for asynchronous processing.
Headers
  • The key of the asynchronous operations associated with an AI Data Platform instance. Use GetAsyncOperation with this key to track the status of the request.
  • For optimistic concurrency control. See `if-match`.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : GitFolder
Type: object
A workspace Git folder and its repository, branch, and connectivity settings.
Show Source
  • Minimum Length: 1
    Maximum Length: 400
    Git branch name that is cloned.
  • Minimum Length: 1
    Maximum Length: 255
    Key of the credential containing the Git server's TLS CA certificate, returned by credential listings filtered by displayName. Required when isPrivateConnectivityEnabled is true.
  • Minimum Length: 0
    Maximum Length: 1000
    Short description about the git repository.
  • folderMetadata
    Additional Properties Allowed: additionalProperties
    The metadata about the folder, like branchName.
  • Minimum Length: 1
    Maximum Length: 1000
    Workspace-relative path of the Git folder, without a leading slash (for example, `sample-repo`). The folder is located at `/Workspace/`.
  • Key of the private network profile used for Git connectivity, returned by private network profile listings filtered by name. Required when isPrivateConnectivityEnabled is true.
  • Maximum Length: 200
    Default Value: GIT
    key corresponding to Git service provider in git provider table.
  • Minimum Length: 1
    Maximum Length: 1000
    Git repository url used to clone.
  • Whether this Git folder uses private network connectivity.
  • SparseCheckoutDetails
    Sparse checkout configuration for a git repository. Only cone mode is supported. Specify only when creating a sparse git folder; sparse checkout cannot be enabled later for a non-sparse git folder. For sparse git folders, settings updates can change cone folder patterns but cannot enable or disable sparse checkout.
Nested Schema : folderMetadata
Type: object
Additional Properties Allowed
Show Source
The metadata about the folder, like branchName.
Nested Schema : SparseCheckoutDetails
Type: object
Sparse checkout configuration for a git repository. Only cone mode is supported. Specify only when creating a sparse git folder; sparse checkout cannot be enabled later for a non-sparse git folder. For sparse git folders, settings updates can change cone folder patterns but cannot enable or disable sparse checkout.
Show Source
  • Default Value: CONE
    Allowed Values: [ "CONE" ]
    Sparse checkout matching mode. Git supports cone and non-cone sparse checkout pattern styles; AIDP supports cone mode only.
  • patterns
    Minimum Number of Items: 0
    Maximum Number of Items: 100
    Repository-root-relative folder paths to include in the sparse worktree. Cone patterns apply only to folders; root-level files in the repository are always materialized. Empty or omitted patterns materialize root-level files only.
Nested Schema : additionalProperties
Type: object
Nested Schema : patterns
Type: array
Minimum Number of Items: 0
Maximum Number of Items: 100
Repository-root-relative folder paths to include in the sparse worktree. Cone patterns apply only to folders; root-level files in the repository are always materialized. Empty or omitted patterns materialize root-level files only.
Show Source

401 Response

Unauthorized (missing or expired credentials, and so on).
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

404 Response

Not Found. The requested resource was not found.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

409 Response

Conflict. Request conflicts with the current state of the resource.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

412 Response

Precondition Failed (One or more conditions in request failed).
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

429 Response

Too Many Requests. Too many requests sent to the server in a short period.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

500 Response

Internal Server Error. The server encountered an unexpected condition preventing fulfilment of the request.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

Default Response

Unknown Error. Error is not recognized by the system.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source
Back to Top