Log SignUpServiceUpdaterJob sidekiq package args

[rileyanderson]

Summary

• Clean up logging when job fails.
  • log attributes from sidekiq attr_package since it expires
  • move exception message to log payload
  • log package key for tracking purposes
  • remove job retry limit
  • bump attr_package expiration to match total possible job retry time (~21 days)

Related issue(s)

• Update SignUpServiceUpdaterJob retries exhausted va.gov-team#82978

Testing

• Test the retries_exhausted block functionality:
• In rails console -rails c

# 1. Create attr package

require 'sidekiq/attr_package'

attr_package_key = Sidekiq::AttrPackage.create( icn: 'some-icn', signature_name: 'some-name', version: 'some-version' )

# 2. create sidekiq job and exception

job = { args: [attr_package_key] }.as_json
exception = StandardError.new('some-error')

# 3. call retries_exhausted block

TermsOfUse::SignUpServiceUpdaterJob.sidekiq_retries_exhausted_block.call(job, exception)

You should see a log like:

Rails -- [TermsOfUse][SignUpServiceUpdaterJob] retries exhausted -- { :icn => "some-icn", :exception_message => "some-error", :attr_package_key => "0c115b48be89fb8c5fc82c6ef4e10254e67274cab850b5a03ab6ec048e926b12" }

What areas of the site does it impact?

Terms of use

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected