Skip to content
Pricing
Search
Results from:
Site
0
Blog
0
Docs
0
Images
0
Orbs
0
Resources
0
Site
0

No results for site

Blog
0

No results for blog

Docs
0

No results for docs

Images
0

No results for images

Orbs
0

No results for orbs

Resources
0

No results for resources

View entire changelog

Audit Log event changes coming in 30 days

Aug 21, 2024

Maintenance

We will be removing the vcs_branch field from the payload column in following audit events:

  • workflow.start
  • workflow.error
  • workflow.job.finish
  • workflow.job.context.request
  • workflow.schedule.start

The field has been moved to a new event associated with each pipeline named trigger_event.create.

Audit logs are exported in CSV format. Currently workflow.start event payload column looks like this:

{“job”:{},”workflow”:{“id”:”00000000-0000-0000-0000-000000000000”, “name”:”test-and-build”,”vcs_branch”:”my-feature-branch”}}

After September 21, 2024, any future event will not include the vcs_branch field, all existing events will remain unmodified:

{“job”:{},”workflow”:{“id”:”00000000-0000-0000-0000-000000000000”, “name”:”test-and-build”}}

The VCS data has been moved to a new trigger_event.create event payload column that is recorded for each created pipeline:

{“pipeline_id”:”00000000-0000-0000-0000-000000000000”, “config_source”:”vcs”, “trigger_source”:”webhook”, “branch”:”my-feature-branch”, “tag”:”my-tag”}

If the vcs_branch field in the payload column is used, customers will need to update their usage to point to the new trigger_event.create, otherwise no action is required.

>Previous changes