Move current gateway key id from environment variable to datastore #49
Labels
Milestone
Comments
1 task
kodiakhq bot
pushed a commit
to relaycorp/relaynet-core-js
that referenced
this issue
Nov 26, 2021
…eStore (#372) To help implement relaycorp/awala-gateway-internet#49 and relaycorp/awala-pong#26 Fixes #55. TODO - [x] Remove certs from private key store.
github-actions bot
pushed a commit
to relaycorp/relaynet-core-js
that referenced
this issue
Nov 26, 2021
…eStore (#372) To help implement relaycorp/awala-gateway-internet#49 and relaycorp/awala-pong#26 Fixes #55. TODO - [x] Remove certs from private key store. [skip ci] 020e40c
kodiakhq bot
pushed a commit
that referenced
this issue
Nov 30, 2021
So that we can rotate certificates. Fixes #49 TODO - [x] Move certificates from private key store to certificate store. - [x] Write migration script. - [x] Delete all references to `GATEWAY_KEY_ID` env var - [x] Alter `/cogrpc/service.spec.ts` to use real MongoDB instead of complicated mocks. - [x] Remove `retrieveOwnCertificates`. - [x] Remove all `VAULT_*` env vars from functional test dir.
|
🎉 This issue has been resolved in version 1.27.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specifying the current key id in the
GATEWAY_KEY_IDenvironment variable makes it extremely cumbersome to bootstrap a new environment or do key rotation, so we should store that pointer to the current key id in a persistent data store like etcd or MongoDB.Equivalent issue in pong service: relaycorp/awala-pong#26
The text was updated successfully, but these errors were encountered: