feat : Action Log

[ShadeWyrm]

1. Provides access to an individual forms audit log.

To access Audit Logs, simply go to the form settings page, and click download activity log!~ Events can take up to 5 minutes to be available in the dynamodb and thus appear in the log.

2. Moves all Event Log actions "Details" from strings into a shared library for further expansion.

All audit log entries now require a matching type.

3. Parameterized Audit Log Details

All audit log details entries now require typesafe parameters defined. These are then passed as JSON Params to be translated.

Closes #6283

[github-actions]

🧪 Review environment

https://v3neitutwtf6l22nlrgcaedtru0ftdyr.lambda-url.ca-central-1.on.aws/

[anikbrazeau]

Do we potentially also need the detailed entities to be defined / captured bilingually as well? Are these currently outside the translation files?

Options/Attributes:

• ${EN_securityAttribute} / ${FR_securityAttribute}
  • Unclassified/Protected A/Protected B, Non-classifié/Protégé A/Protégé B
• ${EN_formPurpose} / ${FR_formPurpose}
  • Administrative/Non-administrative, Administratif/Non-administratif
• ${EN)saveAndResume} / ${FR_saveAndResume}
  • ON/OFF, Activée/Désactivée
• ${EN_enabled} / ${FR_enabled}
  • ON/OFF, Activée/Désactivée
• ${EN_throttlingRate} / ${FR_throttlingRate}
  • 500 requests per minute/1000 requests per minute, 500 demandes par minute/1000 demandes par minute
• ${format}
  • HTML, CSV, JSON

[ShadeWyrm]

Do we potentially also need the detailed entities to be defined / captured bilingually as well? Are these currently outside the translation files?

Right! I'll add a small bit for translating params next.

[anikbrazeau]

Another possible enhancement:

If we wanted to potentially simplify our lives in the future, we could also store "objects"/"variables" to build out the strings.

Option 1: [ User ] [ Action ] [Object ] [ Detail ] at [ Date ] [ Timestamp ]
Option 2: [ Object ] [ Detail ] by [ User ] at [ Date ] [ Timestamp ]

With [User] = [AccountEmailAddress]
With [Object] = [Asset] or [Setting name]
With [Detail] = [ID] or [From][To]

[ShadeWyrm]

Another possible enhancement:

If we wanted to potentially simplify our lives in the future, we could also store "objects"/"variables" to build out the strings.

Option 1: [ User ] [ Action ] [Object ] [ Detail ] at [ Date ] [ Timestamp ] Option 2: [ Object ] [ Detail ] by [ User ] at [ Date ] [ Timestamp ]

With [User] = [AccountEmailAddress] With [Object] = [Asset] or [Setting name] With [Detail] = [ID] or [From][To]

That's what we're doing for the most part.

{"eventDesc":"Updated form name to {{newFormName}}","newFormName":"Form"}

[bryan-robitaille]

The code looks good to me. Two small suggestions...

[bryan-robitaille]

I might suggest to move this to the auditLogs module and make it an internal function _getUserEmails. If another developer were to use the function for a different feature/context it could be problematic from a security perspective.

[bryan-robitaille]

I'm wondering if we can move to a static signature for the logEvent function. The ...args collector is often used in funtions that can have multiple signatures and then goes through a type check to validate which signature to use. In this case we know the args so I'm wondering if there is a less complex way of typing this.