You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+30-1Lines changed: 30 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Add this action to your workflow after checking out your repository:
20
20
21
21
This action reads the `.fleetControl/configurationDefinitions.yml` file from your repository and outputs the configuration definitions. The action expects the file to be present after the repository has been checked out.
22
22
23
-
### Example Workflow
23
+
### Example Workflow For Releasing a New Agent Version
24
24
25
25
```yaml
26
26
name: Process Agent Metadata
@@ -34,10 +34,35 @@ jobs:
34
34
steps:
35
35
- name: Checkout repository
36
36
uses: actions/checkout@v4
37
+
with:
38
+
ref: v1.0.0 # the release tag for the version being released
37
39
38
40
- name: Read agent metadata
39
41
uses: newrelic/agent-metadata-action@v1
40
42
with:
43
+
version: 1.0.0 # only required if different from ref tag
44
+
cache: true # Optional: Enable Go build cache (default: true)
45
+
```
46
+
47
+
### Example Workflow For Updating Docs Metadata on an Existing Agent Version
48
+
49
+
The docs header contains things like a bug fix list, a list of features, etc for the given agent version. These
50
+
will be updated after the initial agent version has been created so checking out the agent repo is not required.
51
+
52
+
```yaml
53
+
name: Process Agent Metadata
54
+
on:
55
+
push:
56
+
branches: [main]
57
+
58
+
jobs:
59
+
read-metadata:
60
+
runs-on: ubuntu-latest
61
+
steps:
62
+
- name: Read agent metadata
63
+
uses: newrelic/agent-metadata-action@v1
64
+
with:
65
+
version: 1.0.0 # required in the docs case
41
66
cache: true # Optional: Enable Go build cache (default: true)
42
67
```
43
68
@@ -57,6 +82,10 @@ configurationDefinitions:
57
82
schema: "./schemas/config-schema.json"
58
83
```
59
84
85
+
**All fields are required.** The action validates each configuration entry and will fail with a clear error message if any required field is missing.
86
+
87
+
**Schema files** are automatically base64-encoded and embedded in the output. Schema paths must be relative to the `.fleetControl` directory and cannot use directory traversal (`..`) for security.
0 commit comments