technical_services
Overview
Name | technical_services |
Type | Resource |
Id | pagerduty.service_dependencies.technical_services |
Fields
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
Name | Accessible by | Required Params | Description |
---|---|---|---|
get_technical_service_service_dependencies | SELECT | id | 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 | 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 | |
_get_technical_service_service_dependencies | EXEC | id | 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 |
delete_service_dependency | EXEC | 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 |