CLDSRV-890: Log lifecycle expiration events in server access logs

[dvasilas]

Add lifecycle expiration deletions to access logs.

For lifecycle expiration events:

• Operation: S3.EXPIRE.OBJECT
• Requester: ScalityS3LifecycleService
• ClientIP/httpCode/timing/auth: undefined (log-courier will write - or "-")

Test plan

• Add lifecycle expiration to workbench
• Add end-to-end tests in log-courier

[bert-e]

Hello dvasilas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[claude]

LGTM

Review by Claude Code

[claude]

LGTM

Review by Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 91.66667% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.37%. Comparing base (c1d3d6a) to head (b90440f).
⚠️ Report is 2 commits behind head on development/9.2.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
lib/routes/routeBackbeat.js	60.00%	2 Missing ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
lib/utilities/serverAccessLogger.js	83.40% <100.00%> (+1.38%)	⬆️
lib/routes/routeBackbeat.js	76.73% <60.00%> (-0.12%)	⬇️

... and 2 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.2    #6150      +/-   ##
===================================================
+ Coverage            84.29%   84.37%   +0.08%     
===================================================
  Files                  204      204              
  Lines                13151    13175      +24     
===================================================
+ Hits                 11086    11117      +31     
+ Misses                2065     2058       -7     

Flag	Coverage Δ
file-ft-tests	67.59% <20.83%> (-0.10%)	⬇️
kmip-ft-tests	28.20% <4.16%> (-0.05%)	⬇️
mongo-v0-ft-tests	68.90% <20.83%> (-0.02%)	⬇️
mongo-v1-ft-tests	68.81% <20.83%> (-0.09%)	⬇️
multiple-backend	35.27% <20.83%> (-0.03%)	⬇️
sur-tests	35.71% <4.16%> (-0.06%)	⬇️
sur-tests-inflights	37.58% <4.16%> (-0.07%)	⬇️
unit	69.99% <83.33%> (+0.02%)	⬆️
utapi-v2-tests	34.48% <4.16%> (-0.06%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dvasilas]

/approve

[bert-e]

Conflict

A conflict has been raised during the creation of
integration branch w/9.3/improvement/CLDSRV-890-log-lifecycle-expiration-events with contents from improvement/CLDSRV-890-log-lifecycle-expiration-events
and development/9.3.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.3/improvement/CLDSRV-890-log-lifecycle-expiration-events origin/development/9.3
 git merge origin/improvement/CLDSRV-890-log-lifecycle-expiration-events
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.3/improvement/CLDSRV-890-log-lifecycle-expiration-events

The following options are set: approve

[dvasilas]

ping

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge improvement/CLDSRV-890-log-lifecycle-expiration-events into
  development/9.2
• w/9.3/improvement/CLDSRV-890-log-lifecycle-expiration-events will be merged into development/9.3
• w/9.4/improvement/CLDSRV-890-log-lifecycle-expiration-events will be merged into development/9.4

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.8
• development/9.0
• development/9.1

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

Build failed

The build for commit did not succeed in branch w/9.3/improvement/CLDSRV-890-log-lifecycle-expiration-events

The following options are set: approve

[bert-e]

Build failed

The build for commit did not succeed in branch w/9.4/improvement/CLDSRV-890-log-lifecycle-expiration-events

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/9.2

• ✔️ development/9.3

• ✔️ development/9.4

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.8
• development/9.0
• development/9.1

Please check the status of the associated issue CLDSRV-890.

Goodbye dvasilas.

The following options are set: approve