Created audit logged JDBC connection for Postgres based Datalinks

[jdunkerley]

New feature in the Standard.Base.Enso_Cloud library, allowing us to write an "audit" message to the cloud.

• No read support from the audit log at present.
• Should have the ability to be used from Enso code but main focus is Java auditing.
• Ideally, posting the audit message is a background worker task.
• Must ensure that background task completes prior to engine exit.

Audited JDBC Proxy object is returned instead of the base JDBC proxy.

• Should have the same API as we have on a JDBC connection.
• Should be opaque to the end user.
• All data link Postgreses should use this.

While not this task, the Snowflake JDBC connection will likewise be sat behind the same.

Eventually, we can also allow the user to opt into auditing all JDBC actions.

[radeusgd]

Probably worth describing how hard it is to still go around this wrapping using reflection (try out in practice).

[radeusgd]

• All data link Postgreses should use this.

Should this be used with Postgres connections established through any data link, or only through data links that are on the Enso Cloud? Should maybe the data link have an audit : boolean flag on it (defaulted to true in the cloud GUI)?

[radeusgd]

• All data link Postgreses should use this.

Should this be used with Postgres connections established through any data link, or only through data links that are on the Enso Cloud? Should maybe the data link have an audit : boolean flag on it (defaulted to true in the cloud GUI)?

Decided that for now we will audit all connections opened through any datalink regardless of source. That is because it is trivial to copy a cloud datalink to the local machine.

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2024-04-29):

Progress: Starting work on Audited Postgres connection. Creating stub for the AuditedConnection, implementing sending audit logs in background. WIP. It should be finished by 2024-05-07.

Next Day: Next day I will be working on the same task. Continue with implementation. Write tests for audit and for the Postgres connection in particular. Add log functionality to cloud mock for easier testing.

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2024-04-30):

Progress: Implemented logic for sending audit logs. Added simple tests. Work on integrating audited connection in Postgres JDBC. It should be finished by 2024-05-07.

Next Day: Next day I will be working on the same task. Fix failures to send the logs. Add tests for DB. Connect everything together.

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2024-05-02):

Progress: Added tests for logs. Tested them on the prod Cloud. Debugged failures. Reported problems to the Cloud team. Implemented a workaround. Debugged problems with Enso_Project returning wrong project reference / not working from Java - filed an Issue. For now logs stay without project name. Continued implementation of the Audited JDBC connection. PoC integration with Postgres datalink - first SQL audit logs visible. It should be finished by 2024-05-07.

Next Day: Next day I will be working on the same task. Implement the Cloud Mock for logs for easier testing. Correlate asset id of the datalink with its connection.

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2024-05-06):

Progress: Fixed signature extraction in the Types prototype and added more tests for it. Implemented the Cloud Mock for logs. Added tests for SQL auditing. Thinking how to integrate asset id correlation. It should be finished by 2024-05-07.

Next Day: Next day I will be working on the same task. Create the PR. Plan followup work.

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2024-05-07):

Progress: Final touches - improved the tests a bit. Created follow up tickets. Put up the PR. It should be finished by 2024-05-07.

Next Day: Next day I will be working on the #9673 task. Work on next tasks.

[enso-bot]

Radosław Waśko reports a new 🔴 DELAY for yesterday (2024-05-08):

Summary: There is 1 day delay in implementation of the Created audit logged JDBC connection for Postgres based Datalinks (#9599) task.
It will cause 0 days delay for the delivery of this weekly plan.

Delay Cause: some more work was needed, also fixing some partially related problems

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2024-05-08):

Progress: Added some missing implementations in AuditedStatement that i forgot about earlier. Refactor table display: it regressed due to private keyword changes and was untested; removed some duplicate code. Improved error message for SQLite over remote backend. Work on finishing the follow up PR for license tool. It should be finished by 2024-05-08.

Next Day: Next day I will be working on the #9812 task. Get the PRs ready for merge. Work on Types.