Skip to content

Consume Service Catalog Information as a Source of Truth #631

@conallob

Description

@conallob

Is your feature request related to a problem? Please describe.

I would like to consume service catalog information, as a source of truth to help join different services together.

Describe the solution you'd like

I can associate the git repositories and slack channel(s) of a team with a service catalog, such as backstage.io, incident.io/catalog or cortex.io . This source of truth could be used to inform team slack channels whenever a pull/merge request is opened in a team's git repository.

Describe alternatives you've considered

None at this time

Additional context

One of the primary challenges for a service catalog is keeping the information up to date. Consuming the information for configuring bots is one of the ways to continuously scrutinize the data, while simultaneously providing value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions