Secrets: Implement migration of secrets from plugin back to unified secrets (#53561)
* initial cut at migration from plugin * create new migration from plugin * only migrate to or from, not both * remove cfg check from plugin migration itself * update comments, clean up secret after migration * add better error handling * hook up REST API with migrations * Minor fixes * fix wire injection issue * modify migrator to access plugin calls directly. create unit tests * change pre-migration checks in admin api * stop plugin after migrating from it * fix compile issues after merge * add comment about migration * fix linting issue * bleh, fix unit test * fix another unit test * update plugin error fatal flag after a migration from the plugin * add extra logging to migration * make linter happy Co-authored-by: Leandro Deveikis <leandro.deveikis@gmail.com>
This commit is contained in:
co-authored by
Leandro Deveikis
parent
c8f2cd2599
commit
277ea836b6
@@ -88,7 +88,7 @@ func TestLockAndRelease(t *testing.T) {
|
||||
|
||||
err2 := sl.acquireForRelease(context.Background(), operationUID, duration)
|
||||
require.Error(t, err2, "We should expect an error when trying to get the second lock")
|
||||
require.Equal(t, "there is already a lock for this operation", err2.Error())
|
||||
require.Equal(t, "there is already a lock for this actionName: "+operationUID, err2.Error())
|
||||
|
||||
err3 := sl.releaseLock(context.Background(), operationUID)
|
||||
require.NoError(t, err3)
|
||||
|
||||
Reference in New Issue
Block a user