technical_services

Creates, updates, deletes, gets or lists a technical_services resource.

Overview

Name	technical_services
Type	Resource
Id	pagerduty.service_dependencies.technical_services

Fields

The following fields are returned by SELECT queries:

get_technical_service_service_dependencies

An array of service relationships.

Name	Datatype	Description
id	string
dependent_service	object	The reference to the service that is dependent on the technical service.
supporting_service	object	The reference to the service that supports the technical service.
type	string

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
get_technical_service_service_dependencies	select	id	Accept, Content-Type	Get all immediate dependencies of any technical service. Technical services are also known as services. For more information see the API Concepts Document Scoped OAuth requires: services.read
create_service_dependency	insert		Accept, Content-Type	Create new dependencies between two services. Business services model capabilities that span multiple technical services and that may be owned by several different teams. A service can have a maximum of 2,000 dependencies with a depth limit of 100. If the limit is reached, the API will respond with an error. For more information see the API Concepts Document Scoped OAuth requires: services.write
delete_service_dependency	exec		Accept, Content-Type	Disassociate dependencies between two services. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the API Concepts Document Scoped OAuth requires: services.write
_get_technical_service_service_dependencies	exec	id	Accept, Content-Type	Get all immediate dependencies of any technical service. Technical services are also known as services. For more information see the API Concepts Document Scoped OAuth requires: services.read

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

Name	Datatype	Description
id	string	The ID of the resource.
Accept	string	The Accept header is used as a versioning header.
Content-Type	string

SELECT examples

get_technical_service_service_dependencies

Get all immediate dependencies of any technical service.
Technical services are also known as services.

For more information see the API Concepts Document

Scoped OAuth requires: services.read

SELECT
id,
dependent_service,
supporting_service,
type
FROM pagerduty.service_dependencies.technical_services
WHERE id = '{{ id }}' -- required
AND Accept = '{{ Accept }}'
AND Content-Type = '{{ Content-Type }}'
;

INSERT examples

create_service_dependency

Create new dependencies between two services.

Business services model capabilities that span multiple technical services and that may be owned by several different teams.

A service can have a maximum of 2,000 dependencies with a depth limit of 100. If the limit is reached, the API will respond with an error.

For more information see the API Concepts Document

Scoped OAuth requires: services.write

INSERT INTO pagerduty.service_dependencies.technical_services (
data__relationships,
Accept,
Content-Type
)
SELECT 
'{{ relationships }}',
'{{ Accept }}',
'{{ Content-Type }}'
RETURNING
relationships
;

Manifest

# Description fields are for documentation purposes
- name: technical_services
  props:
    - name: relationships
      value: array
      description: |
        List of all service dependencies to be created.
    - name: Accept
      value: string
      description: The `Accept` header is used as a versioning header.
    - name: Content-Type
      value: string

Lifecycle Methods

delete_service_dependency

Disassociate dependencies between two services.

Business services model capabilities that span multiple technical services and that may be owned by several different teams.

For more information see the API Concepts Document

Scoped OAuth requires: services.write

EXEC pagerduty.service_dependencies.technical_services.delete_service_dependency 
@Accept='{{ Accept }}', 
@Content-Type='{{ Content-Type }}' 
@@json=
'{
"relationships": "{{ relationships }}"
}'
;

_get_technical_service_service_dependencies

Get all immediate dependencies of any technical service.
Technical services are also known as services.

For more information see the API Concepts Document

Scoped OAuth requires: services.read

EXEC pagerduty.service_dependencies.technical_services._get_technical_service_service_dependencies 
@id='{{ id }}' --required, 
@Accept='{{ Accept }}', 
@Content-Type='{{ Content-Type }}'
;