Create Manually Managed App Resource
Create a manually managed app resource tracked directly by ConductorOne under an existing resource type.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, refer to the c1TokenSource.Token() function.
Path Parameters
The ID of the app to create the resource under.
The resource type ID that classifies this resource.
Body
The request message for creating a manually managed app resource.
The display name for the new resource.
Bounded key/value metadata bag for IaC marking and customer tags.
See .rfcs/object-annotations.md §2. Limits: ≤16 entries; keys 1–128
chars matching ^[A-Za-z][A-Za-z0-9._/-]{0,127}$; values 0–256 chars
matching URL-safe ASCII; total serialized ≤4096 bytes. Keys starting
with c1/ are reserved for server-managed use and rejected on write.
Well-known keys: managed_by, iac_workspace,
iac_resource_address, iac_tool_version.
An optional description for the new resource.
If supplied, it's implied that the resource is created before sync and needs to be merged with connector resource.
C1 user IDs to assign as owners of this resource.
Response
The response message for creating a manually managed app resource.
The response message for creating a manually managed app resource.
The app resource message is a single resource that can have entitlements.
This message contains a oneof named metadata. Only a single field of the following list may be set at a time:
- secretTrait