Fix samples descriptions for marketplace (#23)

ehl-jf · web-flow · commit 6f29c1d9bbbc · 2025-05-13T08:49:25.000+02:00
diff --git a/samples/artifactory/AFTER_CREATE/check-image-signature/manifest.json b/samples/artifactory/AFTER_CREATE/check-image-signature/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "check-image-signature",
-    "description": "Check a docker image signature",
+    "description": "This worker demonstrates a signature validation scenario. After a Docker image has been uploaded, the worker verifies if the image is signed by checking for the presence of a signature file (e.g., `.sig` file generated by cosign). If the image is not signed, the worker removes it.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/AFTER_CREATE/copy-deb-and-rpm/package.json b/samples/artifactory/AFTER_CREATE/copy-deb-and-rpm/package.json
@@ -1,6 +1,6 @@
 {
   "name": "copy-deb-and-rpm",
-  "description": "Run a script on AFTER_CREATE",
+  "description": "This worker script is designed to handle package copy operations between repositories in a JFrog Artifactory environment. It monitors specified repositories for newly created `.deb` and `.rpm` files, parses the file paths using a predefined layout, and copies the files to designated target repositories.",
   "version": "1.0.1",
   "scripts": {
     "deploy": "jf worker deploy",
diff --git a/samples/artifactory/AFTER_DOWNLOAD/report-download-to-external-endpoint/manifest.json b/samples/artifactory/AFTER_DOWNLOAD/report-download-to-external-endpoint/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "report-download-to-external-endpoint",
-    "description": "Report download to external endpoint",
+    "description": "This worker listens to the `AFTER_DOWNLOAD` event in JFrog Artifactory and notifies an external endpoint when a file is downloaded. The worker logs the artifact's details, the repository, and the user responsible for the download.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_COPY/restrict-overwrite/manifest.json b/samples/artifactory/BEFORE_COPY/restrict-overwrite/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "restrict-overwrite",
-    "description": "Restrict overwrite",
+    "description": "The \"Restrict Overwrite: Before Copy\" worker script enforces immutability by preventing overwrites of artifacts during the \"copy\" operation in JFrog Artifactory. It ensures that artifacts cannot be accidentally replaced, maintaining consistency and integrity across deployments.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_CREATE/restrict-overwrite/manifest.json b/samples/artifactory/BEFORE_CREATE/restrict-overwrite/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "restrict-overwrite",
-    "description": "Restrict overwrite",
+    "description": "The \"Restrict Overwrite: Before Create\" worker script enforces immutability by preventing overwrites of artifacts during the \"create\" operation in JFrog Artifactory. It ensures that artifacts cannot be accidentally replaced, maintaining consistency and integrity across deployments.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_DOWNLOAD/resctrict-download-if-no-xray-scan-since/manifest.json b/samples/artifactory/BEFORE_DOWNLOAD/resctrict-download-if-no-xray-scan-since/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "resctrict-download-if-no-xray-scan-since",
-    "description": "Resctrict download if no xray scan since",
+    "description": "This worker is triggered by the `BEFORE_DOWNLOAD` event of Artifactory. Its primary purpose is to restrict downloads of artifacts that have not undergone an Xray scan within a specified threshold duration. This ensures artifacts comply with security policies by enforcing timely scans.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_DOWNLOAD/restrict-download-by-property-value/manifest.json b/samples/artifactory/BEFORE_DOWNLOAD/restrict-download-by-property-value/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "restrict-download-by-property-value",
-    "description": "Restrict download by property value",
+    "description": "This worker is triggered by the `BEFORE_DOWNLOAD` event of Artifactory. Its primary purpose is to block artifact downloads if the artifact contains certain forbidden properties with restricted values. This ensures compliance with organizational policies by preventing downloads of restricted artifacts.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_DOWNLOAD/restrict-download-on-xray-critical-issues/manifest.json b/samples/artifactory/BEFORE_DOWNLOAD/restrict-download-on-xray-critical-issues/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "restrict-download-on-xray-critical-issues",
-    "description": "Restrict download on xray critical issues",
+    "description": "This worker is triggered by the `BEFORE_DOWNLOAD` event of Artifactory. Its primary purpose is to block artifact downloads if the number of critical security issues in JFrog Xray exceeds a defined threshold. The worker ensures compliance with security policies by preventing downloads of artifacts with excessive vulnerabilities.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_MOVE/restrict-overwrite/manifest.json b/samples/artifactory/BEFORE_MOVE/restrict-overwrite/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "restrict-overwrite",
-    "description": "Restrict overwrite",
+    "description": "The \"Restrict Overwrite: Before Move\" worker script enforces immutability by preventing overwrites of artifacts during the \"move\" operation in JFrog Artifactory. It ensures that artifacts cannot be accidentally replaced, maintaining consistency and integrity across deployments.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_PROPERTY_CREATE/property-creation-permission/manifest.json b/samples/artifactory/BEFORE_PROPERTY_CREATE/property-creation-permission/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "property-creation-permission",
-    "description": "Validate property creation permission",
+    "description": "This worker is triggered by the `BEFORE_PROPERTY_CREATE` event in JFrog Artifactory. Its primary purpose is to enforce a policy where only users with admin privileges can create artifact properties.",
     "secrets": {},
     "filterCriteria": {
         "artifactFilterCriteria": {
diff --git a/samples/artifactory/BEFORE_UPLOAD/allow-upload-by-pattern/manifest.json b/samples/artifactory/BEFORE_UPLOAD/allow-upload-by-pattern/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "allow-upload-by-pattern",
-    "description": "Allow upload by pattern",
+    "description": "This worker script ensures that artifact uploads are allowed only if the target path matches a predefined pattern. This pattern is specified using a regular expression (`authorizedPathRegEx`). The script validates the repository path (`repoPath`) and blocks uploads that do not comply with the pattern.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_UPLOAD/check-project-repository/manifest.json b/samples/artifactory/BEFORE_UPLOAD/check-project-repository/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "check-project-repository",
-    "description": "Check that an image is uploaded to the correct repository",
+    "description": "This worker is designed to intercept the upload of Docker image manifests and ensure that they target the correct project repository. It validates that the Docker image manifest contains a specific label (`org.jfrog.artifactory.projectKey`) and that the target repository is prefixed with the same project key.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_UPLOAD/repo-quota/manifest.json b/samples/artifactory/BEFORE_UPLOAD/repo-quota/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "repo-quota",
-    "description": "Repo quota",
+    "description": "The 'Artifactory Storage Quota Worker' is a script designed to enforce storage limits for repository paths. It allows administrators to configure quotas for artifact storage under specific paths within a repository. If the combined size of existing artifacts and a new upload exceeds the defined quota, the upload is rejected.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/BEFORE_UPLOAD/restrict-overwrite/manifest.json b/samples/artifactory/BEFORE_UPLOAD/restrict-overwrite/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "restrict-overwrite",
-    "description": "Restrict overwrite",
+    "description": "This worker script ensures that overwrites are restricted during the upload of artifacts to configured repositories in JFrog Artifactory. The worker validates if an artifact already exists at the target location and stops the upload process if the file or folder is present.",
     "filterCriteria": {
         "artifactFilterCriteria": {
             "repoKeys": [
diff --git a/samples/artifactory/GENERIC_EVENT/artifact-cleanup/manifest.json b/samples/artifactory/GENERIC_EVENT/artifact-cleanup/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "artifact-cleanup",
-    "description": "Artifact cleanup",
+    "description": "This worker code deletes all artifacts that have not been downloaded for the past 'n time units',which is by default 1 month. It can be run manually from the REST API, using a worker generic event.",
     "secrets": {},
     "sourceCodePath": "./worker.ts",
     "action": "GENERIC_EVENT",
diff --git a/samples/artifactory/GENERIC_EVENT/clean-docker-images/manifest.json b/samples/artifactory/GENERIC_EVENT/clean-docker-images/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "clean-docker-images",
-    "description": "Clean docker images",
+    "description": "This worker script is designed to clean Docker repositories hosted in Artifactory based on configurable cleanup policies. It is useful for managing storage and maintaining repository hygiene.",
     "secrets": {},
     "sourceCodePath": "./worker.ts",
     "action": "GENERIC_EVENT",
diff --git a/samples/artifactory/GENERIC_EVENT/delete-by-property-value/manifest.json b/samples/artifactory/GENERIC_EVENT/delete-by-property-value/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "delete-by-property-value",
-    "description": "Delete by property value",
+    "description": "This worker is designed to delete artifacts from specified repositories based on a property and its value. It allows you to define thresholds for properties and delete artifacts with property values below these thresholds. The worker also supports a dry-run mode to simulate the operation without making any changes.",
     "secrets": {},
     "sourceCodePath": "./worker.ts",
     "action": "GENERIC_EVENT",
diff --git a/samples/artifactory/GENERIC_EVENT/delete-empty-dirs/manifest.json b/samples/artifactory/GENERIC_EVENT/delete-empty-dirs/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "delete-empty-dirs",
-    "description": "Delete empty dirs",
+    "description": "This worker deletes all empty directories found inside any of the given set of paths in your Artifactory repositories. The worker traverses specified directories recursively, checking for empty directories, and deletes them if they are found.",
     "secrets": {},
     "sourceCodePath": "./worker.ts",
     "action": "GENERIC_EVENT",
diff --git a/samples/artifactory/GENERIC_EVENT/remote-backup/manifest.json b/samples/artifactory/GENERIC_EVENT/remote-backup/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "remote-backup",
-    "description": "Remote backup",
+    "description": "This worker copies files from a remote cache to a local 'backup' repository. This ensures that cached artifacts are still available, even after they're removed from the cache.",
     "secrets": {},
     "sourceCodePath": "./worker.ts",
     "action": "GENERIC_EVENT",
diff --git a/samples/artifactory/GENERIC_EVENT/repoStats/manifest.json b/samples/artifactory/GENERIC_EVENT/repoStats/manifest.json
@@ -1,6 +1,6 @@
 {
     "name": "repoStats",
-    "description": "Repo Stats",
+    "description": "This Worker displays certain statistics about requested files.",
     "secrets": {},
     "sourceCodePath": "./worker.ts",
     "action": "GENERIC_EVENT",
diff --git a/samples/artifactory/GENERIC_EVENT/staging/manifest.json b/samples/artifactory/GENERIC_EVENT/staging/manifest.json
@@ -0,0 +1,9 @@
+{
+    "name": "staging-strategy-calculator",
+    "description": "This JFrog Worker calculates the staging strategy for Artifactory builds based on configurable strategies. The worker supports multiple strategies such as 'Gradle', 'Simple Maven', and 'Detailed Maven'. It fetches build information from Artifactory and determines the appropriate release version, target repository, tagging details, and more.",
+    "secrets": {},
+    "sourceCodePath": "./worker.ts",
+    "action": "GENERIC_EVENT",
+    "enabled": false,
+    "debug": true
+}
diff --git a/samples/artifactory/eventCombinationWorkers/mavenSnapshotCleanupWhenRelease/AFTER_CREATE/mavenSnapshotCleanupWhenRelease_afterCreate/README.md b/samples/artifactory/eventCombinationWorkers/mavenSnapshotCleanupWhenRelease/AFTER_CREATE/mavenSnapshotCleanupWhenRelease_afterCreate/README.md
@@ -0,0 +1,74 @@
+# MavenSnapshotCleanupWhenRelease Workers
+
+## Overview
+
+The `afterCreate` and `afterMove` workers work together to clean up Maven snapshot files when their corresponding release files are created or moved in JFrog Artifactory. These workers ensure that obsolete snapshot files are removed once a stable release is available, optimizing storage and maintaining repository hygiene.
+
+## Features
+
+- **Automated Cleanup**: Deletes old Maven snapshot versions when a corresponding release is created or moved.
+- **Event-Driven Execution**: Listens for artifact creation (`afterCreate`) and artifact movement (`afterMove`).
+- **Smart Repository Handling**: Determines snapshot repositories linked to release repositories dynamically.
+- **Logging & Error Handling**: Provides detailed logs for debugging and ensures errors do not block the process.
+
+## Workers
+
+### 1. afterCreate Worker
+
+**Trigger**: Runs when a new artifact is created in a repository.
+
+**Functionality**:
+- Checks if the newly created file is a Maven POM (`.pom` file).
+- Identifies the associated snapshot repository.
+- Cleans up corresponding snapshot versions if applicable.
+
+### 2. afterMove Worker
+
+**Trigger**: Runs when an artifact is moved between repositories.
+
+**Functionality**:
+- Detects when an artifact is moved from a staging or development repository to a release repository.
+- Identifies the related snapshot repository.
+- Cleans up old snapshot versions corresponding to the released artifact.
+
+## How It Works
+
+1. A release POM file is created (afterCreate triggers cleanup of snapshots).
+2. Artifacts are moved from staging to a release repository (afterMove triggers additional cleanup).
+3. The snapshot repository is determined dynamically based on the release repository name.
+4. The corresponding snapshot artifacts are identified and deleted to free up space.
+5. Logs are generated for traceability and debugging.
+
+## Deployment & Configuration
+
+### Parameters
+
+The workers require minimal configuration as they automatically infer the snapshot repository from the release repository.
+
+| **Parameter** | **Type**                    | **Description**                                                                 |
+|---------------|-----------------------------|---------------------------------------------------------------------------------|
+| `context`     | PlatformContext             | Provides API access for repository operations.                                 |
+| `data`        | AfterCreateRequest / AfterMoveRequest | Contains event data, such as repository key and artifact path.               |
+
+### Example Execution
+
+#### After Create Trigger:
+
+```
+curl -u user:apiKey -X POST "${baseUrl}/worker/api/v1/execute/afterCreate" \
+  -H "Content-Type: application/json" \
+  -d '{ "metadata": { "repoPath": { "key": "maven-releases", "path": "com/example/app/1.0.0/app-1.0.0.pom" } } }'
+```
+
+#### After Move Trigger:
+
+```
+curl -u user:apiKey -X POST "${baseUrl}/worker/api/v1/execute/afterMove" \
+  -H "Content-Type: application/json" \
+  -d '{ "sourceRepo": "staging-repo", "targetRepo": "maven-releases", "itemPath": "com/example/app/1.0.0/app-1.0.0.jar" }'
+```
+
+## Best Practices
+
+1. Monitor Logs: Ensure the correct snapshot versions are being removed.
+2. Use with Care: These workers perform deletions; verify configurations to prevent unintended removals.
diff --git a/samples/artifactory/eventCombinationWorkers/mavenSnapshotCleanupWhenRelease/AFTER_MOVE/mavenSnapshotCleanupWhenRelease_afterMove/README.md b/samples/artifactory/eventCombinationWorkers/mavenSnapshotCleanupWhenRelease/AFTER_MOVE/mavenSnapshotCleanupWhenRelease_afterMove/README.md
@@ -0,0 +1,74 @@
+# MavenSnapshotCleanupWhenRelease Workers
+
+## Overview
+
+The `afterCreate` and `afterMove` workers work together to clean up Maven snapshot files when their corresponding release files are created or moved in JFrog Artifactory. These workers ensure that obsolete snapshot files are removed once a stable release is available, optimizing storage and maintaining repository hygiene.
+
+## Features
+
+- **Automated Cleanup**: Deletes old Maven snapshot versions when a corresponding release is created or moved.
+- **Event-Driven Execution**: Listens for artifact creation (`afterCreate`) and artifact movement (`afterMove`).
+- **Smart Repository Handling**: Determines snapshot repositories linked to release repositories dynamically.
+- **Logging & Error Handling**: Provides detailed logs for debugging and ensures errors do not block the process.
+
+## Workers
+
+### 1. afterCreate Worker
+
+**Trigger**: Runs when a new artifact is created in a repository.
+
+**Functionality**:
+- Checks if the newly created file is a Maven POM (`.pom` file).
+- Identifies the associated snapshot repository.
+- Cleans up corresponding snapshot versions if applicable.
+
+### 2. afterMove Worker
+
+**Trigger**: Runs when an artifact is moved between repositories.
+
+**Functionality**:
+- Detects when an artifact is moved from a staging or development repository to a release repository.
+- Identifies the related snapshot repository.
+- Cleans up old snapshot versions corresponding to the released artifact.
+
+## How It Works
+
+1. A release POM file is created (afterCreate triggers cleanup of snapshots).
+2. Artifacts are moved from staging to a release repository (afterMove triggers additional cleanup).
+3. The snapshot repository is determined dynamically based on the release repository name.
+4. The corresponding snapshot artifacts are identified and deleted to free up space.
+5. Logs are generated for traceability and debugging.
+
+## Deployment & Configuration
+
+### Parameters
+
+The workers require minimal configuration as they automatically infer the snapshot repository from the release repository.
+
+| **Parameter** | **Type**                    | **Description**                                                                 |
+|---------------|-----------------------------|---------------------------------------------------------------------------------|
+| `context`     | PlatformContext             | Provides API access for repository operations.                                 |
+| `data`        | AfterCreateRequest / AfterMoveRequest | Contains event data, such as repository key and artifact path.               |
+
+### Example Execution
+
+#### After Create Trigger:
+
+```
+curl -u user:apiKey -X POST "${baseUrl}/worker/api/v1/execute/afterCreate" \
+  -H "Content-Type: application/json" \
+  -d '{ "metadata": { "repoPath": { "key": "maven-releases", "path": "com/example/app/1.0.0/app-1.0.0.pom" } } }'
+```
+
+#### After Move Trigger:
+
+```
+curl -u user:apiKey -X POST "${baseUrl}/worker/api/v1/execute/afterMove" \
+  -H "Content-Type: application/json" \
+  -d '{ "sourceRepo": "staging-repo", "targetRepo": "maven-releases", "itemPath": "com/example/app/1.0.0/app-1.0.0.jar" }'
+```
+
+## Best Practices
+
+1. Monitor Logs: Ensure the correct snapshot versions are being removed.
+2. Use with Care: These workers perform deletions; verify configurations to prevent unintended removals.

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "check-image-signature",`
`3`		`- "description": "Check a docker image signature",`
	`3`	+ "description": "This worker demonstrates a signature validation scenario. After a Docker image has been uploaded, the worker verifies if the image is signed by checking for the presence of a signature file (e.g., `.sig` file generated by cosign). If the image is not signed, the worker removes it.",
`4`	`4`	`"filterCriteria": {`
`5`	`5`	`"artifactFilterCriteria": {`
`6`	`6`	`"repoKeys": [`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "copy-deb-and-rpm",`
`3`		`- "description": "Run a script on AFTER_CREATE",`
	`3`	+ "description": "This worker script is designed to handle package copy operations between repositories in a JFrog Artifactory environment. It monitors specified repositories for newly created `.deb` and `.rpm` files, parses the file paths using a predefined layout, and copies the files to designated target repositories.",
`4`	`4`	`"version": "1.0.1",`
`5`	`5`	`"scripts": {`
`6`	`6`	`"deploy": "jf worker deploy",`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "report-download-to-external-endpoint",`
`3`		`- "description": "Report download to external endpoint",`
	`3`	+ "description": "This worker listens to the `AFTER_DOWNLOAD` event in JFrog Artifactory and notifies an external endpoint when a file is downloaded. The worker logs the artifact's details, the repository, and the user responsible for the download.",
`4`	`4`	`"filterCriteria": {`
`5`	`5`	`"artifactFilterCriteria": {`
`6`	`6`	`"repoKeys": [`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "restrict-overwrite",`
`3`		`- "description": "Restrict overwrite",`
	`3`	`+ "description": "The \"Restrict Overwrite: Before Copy\" worker script enforces immutability by preventing overwrites of artifacts during the \"copy\" operation in JFrog Artifactory. It ensures that artifacts cannot be accidentally replaced, maintaining consistency and integrity across deployments.",`
`4`	`4`	`"filterCriteria": {`
`5`	`5`	`"artifactFilterCriteria": {`
`6`	`6`	`"repoKeys": [`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "resctrict-download-if-no-xray-scan-since",`
`3`		`- "description": "Resctrict download if no xray scan since",`
	`3`	+ "description": "This worker is triggered by the `BEFORE_DOWNLOAD` event of Artifactory. Its primary purpose is to restrict downloads of artifacts that have not undergone an Xray scan within a specified threshold duration. This ensures artifacts comply with security policies by enforcing timely scans.",
`4`	`4`	`"filterCriteria": {`
`5`	`5`	`"artifactFilterCriteria": {`
`6`	`6`	`"repoKeys": [`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "restrict-download-by-property-value",`
`3`		`- "description": "Restrict download by property value",`
	`3`	+ "description": "This worker is triggered by the `BEFORE_DOWNLOAD` event of Artifactory. Its primary purpose is to block artifact downloads if the artifact contains certain forbidden properties with restricted values. This ensures compliance with organizational policies by preventing downloads of restricted artifacts.",
`4`	`4`	`"filterCriteria": {`
`5`	`5`	`"artifactFilterCriteria": {`
`6`	`6`	`"repoKeys": [`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "restrict-download-on-xray-critical-issues",`
`3`		`- "description": "Restrict download on xray critical issues",`
	`3`	+ "description": "This worker is triggered by the `BEFORE_DOWNLOAD` event of Artifactory. Its primary purpose is to block artifact downloads if the number of critical security issues in JFrog Xray exceeds a defined threshold. The worker ensures compliance with security policies by preventing downloads of artifacts with excessive vulnerabilities.",
`4`	`4`	`"filterCriteria": {`
`5`	`5`	`"artifactFilterCriteria": {`
`6`	`6`	`"repoKeys": [`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "property-creation-permission",`
`3`		`- "description": "Validate property creation permission",`
	`3`	+ "description": "This worker is triggered by the `BEFORE_PROPERTY_CREATE` event in JFrog Artifactory. Its primary purpose is to enforce a policy where only users with admin privileges can create artifact properties.",
`4`	`4`	`"secrets": {},`
`5`	`5`	`"filterCriteria": {`
`6`	`6`	`"artifactFilterCriteria": {`