Skip to content

question: vault/ssm/awssecrets testing approach  #6

Open

Description

@klebediev

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

  1. mumoshu commented on Oct 17, 2019

    @mumoshu
    Collaborator

    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.

  2. klebediev commented on Oct 17, 2019

    @klebediev
    ContributorAuthor

    Thanks @mumoshu !

  3. klebediev commented on Oct 18, 2019

    @klebediev
    ContributorAuthor

    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

  4. mumoshu commented on Oct 20, 2019

    @mumoshu
    Collaborator

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

  5. added a commit that references this issue on Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions