You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
There are TODO sections like this one: prerequisites for unit-tests to run successfully (some operations are needed to be run manually from console).
Wondering what's the best way to fully automate tests.
Should vault[/awssecrets/ssm] just be mocked?
Or (at least in case of vault) we may start test vault cluster for example in TestMain() and populate it with test data?
Activity
mumoshu commentedon Oct 17, 2019
Hey! Yeah, generally mocking sounds great, especially or awssecrets and ssm.
If mocking turned too difficult, for Vault, adding a makefile target or a CI step to run vault dev-server before
go testwould be ok, as it's easy.For awssecrets and ssm we don't have reliable implementations of them that run locally.
klebediev commentedon Oct 17, 2019
Thanks @mumoshu !
klebediev commentedon Oct 18, 2019
just in case, found this https://github.com/localstack/localstack
mumoshu commentedon Oct 20, 2019
Oh! I knew localstack but had never realized it supported SSM as well. Thanks a lot for your info!
fix(vault): dedup concurrent reads via singleflight, drop secret cache
Feat/vault provider cache (#1213)