Jim 1c330543a7 fix (oplog keys): fix issue with migration of oplog keys to new tables (#3868) ...

We inadvertently used
kms.GetWrapper(ctx, am.ScopeId, kms.KeyPurposeDatabase)
which resulted in the use of a database key for an oplog entry.
See:
https://github.com/hashicorp/boundary/pull/3665/files#diff-bcf83b5283886c98fc45b6435fdc94d87d545b2768c6beac8acd14eb9d6b13f1

This fixes the issue with the missing "Database" purpose key when
we converted the oplog keys into their own tables.

We chosen to truncate the existing oplog entries to eliminate any
references to a Database kms key in existing oplog entries.

2023-10-23 18:42:23 -04:00

..

01_kms_oplog_schema_version.up.sql

refactor(sql): Reorder and rename oplog kms migrations

2023-09-06 19:55:33 -04:00

02_kms_oplog_collection_version.up.sql

refactor(sql): Reorder and rename oplog kms migrations

2023-09-06 19:55:33 -04:00

03_kms_oplog.up.sql

fix (oplog keys): fix issue with migration of oplog keys to new tables (#3868)

2023-10-23 18:42:23 -04:00

04_alter_oplog_entry.up.sql

refactor(sql): Consolidate changes to oplog_entry into one migration

2023-09-06 20:05:50 -04:00