-
Notifications
You must be signed in to change notification settings - Fork 6
/
action.yml
101 lines (95 loc) · 3.47 KB
/
action.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
---
name: 'Datadog Service Catalog Metadata Provider'
description: 'This is an action which allows you to provide your Datadog Service Catalog metadata to the Datadog Service Catalog'
author: 'Mike Stemle <[email protected]>'
branding:
icon: 'monitor'
color: 'purple'
runs:
using: node20
main: dist/index.cjs
inputs:
# Stuff we need for this action
github-token:
description: 'The GitHub token to use for the action; default is `secrets.GITHUB_TOKEN`'
required: false
org-rules-file:
description: '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.'
required: false
# Stuff we need for the Datadog API
datadog-hostname:
description: 'The Datadog API hostname (this varies by Datadog customer!)'
required: true
default: 'api.datadoghq.com'
datadog-key:
description: 'The Datadog API key'
required: true
datadog-app-key:
description: 'The Datadog Application key'
required: true
# Fields which are common to all schema versions
schema-version:
description: 'The version of the Datadog Service Catalog Schema. For backwards-compatibility reasons, the default is v2. Valid values are `v2` and `v2.1`.'
required: false
default: 'v2'
service-name:
description: 'The name of the service'
required: true
team:
description: 'The team responsible for the service'
required: false
contacts:
description: 'The contacts for the service'
required: false
tags:
description: 'The tags to apply to the service'
required: false
links:
description: 'The links to related to the service'
required: false
integrations:
description: 'The integrations for the service'
required: false
extensions:
description: 'Any custom extensions you wish to use'
required: false
# Fields which are unique to v2
docs:
description: 'The documentation for the service'
required: false
repos:
description: 'The repositories for the service'
required: false
# Fields which are unique to v2.1
application:
description: '(v2.1 only) The name of the application that the service belongs to.'
required: false
description:
description: '(v2.1 only) A description of the service.'
required: false
tier:
description: '(v2.1 only) A representation of how important this service is. You can use any string that conveys meaning for you or your organization.'
required: false
lifecycle:
description: '(v2.1 only) The current life cycle phase of the service. For example: sandbox, staging, production, deprecated'
required: false
# Fields which were added in v2.2
type:
description: 'Type of the service. Examples: "web", "db", "cache", "function", "browser", "mobile", "custom"'
required: false
languages:
description: 'A list of programming languages used.'
required: false
ci-pipeline-fingerprints:
description: 'A set of CI pipeline fingerprints related to the service'
required: false
# These are convenience inputs which are unique to this action.
email:
description: 'The email address of the team responsible for the service'
required: true
slack-support-channel:
description: 'The slack support channel for the service'
required: false
repo:
description: 'The repository URL for the service. This is a convenience input for when you only have one repository for the service.'
required: false