Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question: vault/ssm/awssecrets testing approach #6

Open
klebediev opened this issue Oct 17, 2019 · 4 comments
Open

question: vault/ssm/awssecrets testing approach #6

klebediev opened this issue Oct 17, 2019 · 4 comments

Comments

@klebediev
Copy link
Contributor

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?

@mumoshu
Copy link
Collaborator

mumoshu commented 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 test would be ok, as it's easy.

For awssecrets and ssm we don't have reliable implementations of them that run locally.

@klebediev
Copy link
Contributor Author

Thanks @mumoshu !

@klebediev
Copy link
Contributor Author

klebediev commented Oct 18, 2019

For awssecrets and ssm we don't have reliable implementations of them that run locally.

just in case, found this https://github.com/localstack/localstack

@mumoshu
Copy link
Collaborator

mumoshu commented Oct 20, 2019

Oh! I knew localstack but had never realized it supported SSM as well. Thanks a lot for your info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants