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
feat(upload-artifact): uploads binaries to an oci registry (#22)
* feat(upload-artifact): uploads binaries to an oci registry
* feat(upload-artifact): use README.txt in test action
* feat(upload-artifact): use local oci registry
* feat(upload-artifact): fix sending incorrect size
* feat(upload-artifact): add debug logs
* feat(upload-artifact): verification only with curl
* feat(upload-artifact): add back verification flags
* feat(upload-artifact): add config tests + move env to env.go
* feat(upload-artifact): use filepath.Rel
* feat(upload-artifact): increase upload.go coverage
* feat(upload-artifact): create index even if some binary is not uploaded
* feat(upload-artifact): increase client.go coverage
* feat(upload-artifact): add check to be case insensitive
* feat(upload-artifact): GetFileName use stdlib
* feat(upload-artifact): update README.md with upload artifact
* feat(upload-artifact): back to original .gitignore
* fix: merge issue
### Example Workflow For Updating Docs Metadata for a new/existing Agent Version
@@ -100,6 +109,27 @@ agentControlDefinitions:
100
109
101
110
**Paths must be relative to the `.fleetControl` directory and cannot use directory traversal (`..`) for security.
102
111
112
+
113
+
#### Artifact Upload
114
+
115
+
The agent release workflow supports uploading agent binaries to an OCI registry. This feature is optional and only applies to agent releases (when both `agent-type` and `version` are provided).
116
+
117
+
To enable binary uploads, provide the following inputs:
0 commit comments