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

Add the mapping from HCL -> JSON to the README? #10

Open
virtuald opened this issue Sep 4, 2014 · 7 comments
Open

Add the mapping from HCL -> JSON to the README? #10

virtuald opened this issue Sep 4, 2014 · 7 comments
Labels
v1 Relates to the v1 line of releases

Comments

@virtuald
Copy link

virtuald commented Sep 4, 2014

The mapping from HCL to JSON (and vice versa) isn't immediately clear. I haven't been able to find concrete documentation for this yet. The fixtures help, but there seems to be a mix of valid/invalid examples.

@josephholsten
Copy link

that's why I built hcl2json in #24. would you take a look and tell me what else you'd like in it?

@virtuald
Copy link
Author

I don't really use go for anything, and don't really have the time to do it. pyhcl comes with a similar script called 'hcltool' which does exactly this, however. I imagine they will typically have the same output -- but in the cases they don't,it's probably because HCL is still murkily specified.

@virtuald virtuald mentioned this issue Dec 19, 2014
@josephholsten
Copy link

Would it be useful to have a test suite that allows us to verify the resultant documents are identical at the CLI level? That'll probably be too large to fit into the readme.

@virtuald
Copy link
Author

There sorta already is such a test suite, but I think the key thing missing is a clearer formal specification of the mapping.

@timgent
Copy link
Contributor

timgent commented Aug 31, 2015

+1 for this. The tool is useful, but documentation would help to supplement this. It would still be useful to have a few examples in the docs for how to convert between them, so that at a glance you can see how the mapping works.

@sheerun
Copy link

sheerun commented Mar 1, 2016

Yes, please..

@timgent
Copy link
Contributor

timgent commented Mar 1, 2016

I will rebase this if someone is able to merge it in?
#36

@apparentlymart apparentlymart added the v1 Relates to the v1 line of releases label Aug 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1 Relates to the v1 line of releases
Projects
None yet
Development

No branches or pull requests

5 participants