Namespace Sdk

The OCID of API resource

File location for generated SDK.

The OCID of the compartment in which the resource is created.

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}

A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.

Example: {@code My new resource}

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.

Example: {@code {\"Department\": \"Finance\"}}

The OCID of the resource.

A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in a Failed state.

The current state of the SDK.

• The SDK will be in CREATING state if the SDK creation is in progress.
• The SDK will be in ACTIVE state if create is successful.
• The SDK will be in FAILED state if the create, or delete fails.
• The SDK will be in DELETING state if the deletion in in progress.
• The SDK will be in DELETED state if the delete is successful.

Additional optional configurations passed. The applicable config keys are listed under "parameters" when "/sdkLanguageTypes" is called.

Example: {@code {\"configName\": \"configValue\"}}

The string representing the target programming language for generating the SDK.

Expiry of artifact url.

The time this resource was created. An RFC3339 formatted datetime string.

The time this resource was last updated. An RFC3339 formatted datetime string.