Skip to content
This repository has been archived by the owner on Sep 12, 2019. It is now read-only.

[Compliance] Make encryption_key optional until it is supported? #39

Open
Mr0grog opened this issue Sep 29, 2016 · 0 comments
Open

[Compliance] Make encryption_key optional until it is supported? #39

Mr0grog opened this issue Sep 29, 2016 · 0 comments

Comments

@Mr0grog
Copy link
Contributor

Mr0grog commented Sep 29, 2016

The compliance readme currently lists the encryption_key config property as “not working yet,” but it is still required in the configuration validation routine: https://github.com/stellar/bridge-server/blob/master/src/github.com/stellar/gateway/compliance/config/config.go#L59-L62

Should it be optional until support for it is implemented? If not, we should probably at least update the readme to clarify that you still have to specify it (and it has to be valid).

@jedmccaleb jedmccaleb added this to the after port milestone Oct 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants