Service connectors
Last updated
Was this helpful?
Last updated
Was this helpful?
Returns the requested service connector.
Args: connector_id: ID of the service connector. expand_secrets: Whether to expand secrets or not. hydrate: Flag deciding whether to hydrate the output model(s) by including metadata fields in the response.
Returns: The requested service connector.
true
true
Get a list of all service connectors.
Args: connector_filter_model: Filter model used for pagination, sorting, filtering project_name_or_id: Optional name or ID of the project to filter by. expand_secrets: Whether to expand secrets or not. hydrate: Flag deciding whether to hydrate the output model(s) by including metadata fields in the response.
Returns: Page with list of service connectors matching the filter criteria.
true
false
created
Logical Ops to use to combine filters on list methods.
and
Possible values: 1
20
Updates a service connector.
Args: connector_id: ID of the service connector. connector_update: Service connector to use to update.
Returns: Updated service connector.
Model used for service connector updates.
Most fields in the update model are optional and will not be updated if omitted. However, the following fields are "special" and leaving them out will also cause the corresponding value to be removed from the service connector in the database:
resource_id
fieldexpiration_seconds
fieldIn addition to the above exceptions, the following rules apply:
configuration
and secrets
fields together represent a full
valid configuration update, not just a partial update. If either is
set (i.e. not None) in the update, their values are merged together and
will replace the existing configuration and secrets values.labels
field is also a full labels update: if set (i.e. not
None
), all existing labels are removed and replaced by the new labels
in the update.NOTE: the attributes here override the ones in the base class, so they have a None default value.