This is an example for Lowkey Vault. It shows how you can start Lowkey Vault while using most of the features it provides.
- docker/example.sh shows how you can
- start up your Lowkey Vault container attaching the keyvault.json.hbs backup file from the import sub-folder as well as using an external configuration file named application.properties from the config sub-folder.
- start up an Assumed Identity container listening on port 8080 (only needed for the Managed Identity tests).
- docker-compose/docker-compose.yml shows how to
- start up your container using Docker compose including the import of the keyvault.json.hbs backup and use configuration overrides from application.properties.
- start up an Assumed Identity container listening on port 8080 (only needed for the Managed Identity tests).
- docker-compose-multiarch/docker-compose.yml shows how you need to
change the Docker compose setup to use a multiarch image and achieve the same outcome, i.e.
- import the keyvault.json.hbs backup and load the configuration from application.properties.
- start up an Assumed Identity container listening on port 8080 (only needed for the Managed Identity tests).
- The two sets of tests are the following
- example_test.go contains the core set of tests using the Lowkey Vault container with a
FakeCredential
for authentication. - example_managed_id_test.go is focusing on the changes that are necessary to
allow using the
DefaultAzureCredential
utilizing the fake Managed Identity tokens provided by the Assumed Identity container. For these cases to work, please don't forget to set the following environment variables:IDENTITY_ENDPOINT
pointing to the Assumed Identity containers token endpoint. e.g., http://localhost:8080/metadata/identity/oauth2/tokenIDENTITY_HEADER
using the wordheader
(won't be used, just needed for an exists check)
- example_test.go contains the core set of tests using the Lowkey Vault container with a