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

Investigate Configuration Languages #35

Open
3 tasks
magmastonealex opened this issue Jun 26, 2019 · 1 comment
Open
3 tasks

Investigate Configuration Languages #35

magmastonealex opened this issue Jun 26, 2019 · 1 comment

Comments

@magmastonealex
Copy link
Member

Some teams expressed concern with using YAML since they were not familiar with it.

Investigate some alternatives:

  • JSON
  • Hashicorp Configuration Language
  • YAML, but with some tutorials.
@magmastonealex
Copy link
Member Author

In the second peer usability study, the same team one again expressed concern over YAML causing unnecessary friction.

In particular, the "recipes" section was described as being too verbose, and annoying to configure manually.

We should consider allowing syntax closer to:

etc.

This would mean that packages become an array of strings to parse, rather than an array of objects.

Unfortunately, this would probably be a breaking change, unless we do something really smart with schema.

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

1 participant