arcxp/Datadog Service Catalog Metadata Provider
This is an action which allows you to provide your Datadog Service Catalog metadata to the Datadog Service Catalog
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Mar 4, 2025
- License
- MIT
Pinned Snippet
uses: arcxp/datadog-service-catalog-metadata-provider@e909e3743d666eb3de9a54dbbe2f1251257ac93f # v2.3.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | The GitHub token to use for the action; default is `secrets.GITHUB_TOKEN` | no | — |
| org-rules-file | The path to the org rules file; default is repository `ORG-NAME-HERE/.github` and the `service-catalog-rules.yml` file is expected in the root of that repository. | no | — |
| datadog-hostname | The Datadog API hostname (this varies by Datadog customer!) | yes | api.datadoghq.com |
| datadog-key | The Datadog API key | yes | — |
| datadog-app-key | The Datadog Application key | yes | — |
| schema-version | The version of the Datadog Service Catalog Schema. For backwards-compatibility reasons, the default is v2. Valid values are `v2` and `v2.1`. | no | v2 |
| service-name | The name of the service | yes | — |
| team | The team responsible for the service | no | — |
| contacts | The contacts for the service | no | — |
| tags | The tags to apply to the service | no | — |
| links | The links to related to the service | no | — |
| integrations | The integrations for the service | no | — |
| extensions | Any custom extensions you wish to use | no | — |
| docs | The documentation for the service | no | — |
| repos | The repositories for the service | no | — |
| application | (v2.1 only) The name of the application that the service belongs to. | no | — |
| description | (v2.1 only) A description of the service. | no | — |
| tier | (v2.1 only) A representation of how important this service is. You can use any string that conveys meaning for you or your organization. | no | — |
| lifecycle | (v2.1 only) The current life cycle phase of the service. For example: sandbox, staging, production, deprecated | no | — |
| type | Type of the service. Examples: "web", "db", "cache", "function", "browser", "mobile", "custom" | no | — |
| languages | A list of programming languages used. | no | — |
| ci-pipeline-fingerprints | A set of CI pipeline fingerprints related to the service | no | — |
| The email address of the team responsible for the service | yes | — | |
| slack-support-channel | The slack support channel for the service | no | — |
| repo | The repository URL for the service. This is a convenience input for when you only have one repository for the service. | no | — |
Outputs
no outputs