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

--type string causes Prelude.read: no parse #36

Open
gasi opened this issue Sep 5, 2019 · 2 comments
Open

--type string causes Prelude.read: no parse #36

gasi opened this issue Sep 5, 2019 · 2 comments

Comments

@gasi
Copy link

gasi commented Sep 5, 2019

Repro:

> confcrypt aws add --key "…" --type string --name FOO --value BAR config.econf

Solution:

> confcrypt aws add --key "$CONFCRYPT_KMS_KEY" --type String --name FOO --value bar app_config/dev.econf
-confcrypt aws add --key "$CONFCRYPT_KMS_KEY" --type string --name FOO --value bar app_config/dev.econf
+confcrypt aws add --key "$CONFCRYPT_KMS_KEY" --type String --name FOO --value bar app_config/dev.econf
@fsoikin
Copy link
Contributor

fsoikin commented Sep 5, 2019

This is not technically a bug, is it? The help screen for aws add clearly states:

  -t,--type PARAMETER_TYPE The associated type for the variable. Must be one of
                           [String, Int, Boolean]

@gasi
Copy link
Author

gasi commented Sep 5, 2019

The problem is when you set multiple flags, it prints back your entire config and then Prelude.read: no parse. This could be a more friendly error message that points to the problem. I didn’t figure out the problem until I asked Chris.

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