GCS Artifact Trigger to support updated files, not just newly added
B
Beige Turtle
Description:
Currently, the Harness GCS artifact trigger only fires when a new file/object is added to the bucket. If an existing file is updated (new version uploaded with the same name), the trigger does not detect the change.
Enhancement request:
Enable the GCS artifact trigger to also listen for object updates/modifications in addition to new object creations. This would allow pipelines to run when a file is updated in place, without requiring a new filename.
Impact:
- Current limitation prevents pipelines from running when teams overwrite or update existing files in the GCS bucket.
Use case example:
- Customers with workflows that regenerate or patch files in place (e.g., Terraform outputs updating multiple JSON files) must rename or duplicate files to trigger pipelines, which is inefficient and error-prone.
Log In