This is a fork of Amplify's Python HCL2 repository. This repository went through minor changes to work better with GLITCH and as the changes concern only the structure representation to be compatible with GLITCH we decided not to request updates for the upstream project. The two projects diverge in the representation of some structures and pushing new changes upstream doesn't make sense.
A parser for HCL2 written in Python using Lark. This parser only supports HCL2 and isn't backwards compatible with HCL v1. It can be used to parse any HCL2 config file such as Terraform.
Amplify builds innovative and compelling digital educational products that empower teachers and students across the country. We have a long history as the leading innovator in K-12 education - and have been described as the best tech company in education and the best education company in tech. While others try to shrink the learning experience into the technology, we use technology to expand what is possible in real classrooms with real students and teachers.
Learn more at https://www.amplify.com
python-hcl2 requires Python 3.7 or higher to run.
This package can be installed using pip
pip3 install python-hcl2
import hcl2
with open('foo.tf', 'r') as file:
dict = hcl2.load(file)
For development, tox>=4.0.9
is recommended.
python-hcl2 uses tox
. You will need to install tox with pip install tox
.
Running tox
will automatically execute linters as well as the unit tests.
You can also run them individually with the -e
argument.
For example, tox -e py37-unit
will run the unit tests for python 3.7
To see all the available options, run tox -l
.
To create a new releaes go to Releases page, press 'Draft a new release', create a tag with a version you want to be released, fill the release notes and press 'Publish release'. Github actions will take care of publishing it to PyPi.
If you have any security issue to report, contact project maintainers privately. You can reach us at mailto:[email protected]
We welcome pull requests! For your pull request to be accepted smoothly, we suggest that you:
- For any sizable change, first open a GitHub issue to discuss your idea.
- Create a pull request. Explain why you want to make the change and what it’s for.
We’ll try to answer any PR’s promptly.