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

Terraform: downgrade python-hcl2 from 4.3.2 to 4.3.0 to work around parsing issues (Cherry-pick of #21361) #21365

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

WorkerPants
Copy link
Member

python-hcl2 4.3.1+ has some serious issues with parsing certain kinds of expressions, like multi-line
ternaries. The issues opened can be seen here.

It looks like 4.3.5 has fixed a bunch of the issues, but I'm still seeing some errors on our repo, and I think
it's better to keep to 4.3.0 until the authors of the issues close them and we're sure there are no regressions.

Also, 4.3.0 is still compatible with py3.12, so it doesn't undo the efforts of #20365.

Generated with pants run build-support/bin/generate_builtin_lockfiles.py -- terraform-hcl2-parser.

…arsing issues (#21361)

`python-hcl2` 4.3.1+ has some serious issues with parsing certain kinds
of expressions, like multi-line
ternaries. The issues opened can be seen
[here](https://github.com/amplify-education/python-hcl2/issues?q=is%3Aissue+is%3Aopen+%22unexpected+token%22).

It looks like 4.3.5 has fixed a bunch of the issues, but I'm still
seeing some errors on our repo, and I think
it's better to keep to 4.3.0 until the authors of the issues close them
and we're sure there are no regressions.

Also, 4.3.0 is still compatible with py3.12, so it doesn't undo the
efforts of #20365.

Generated with `pants run
build-support/bin/generate_builtin_lockfiles.py --
terraform-hcl2-parser`.
@huonw
Copy link
Contributor

huonw commented Aug 29, 2024

I have an impression that 2.22.x is very close, so I'm inclined to leave this out of 2.22.x until we cut 2.22.0, and let it flow into 2.22.1. (cc @benjyw as 2.22 release manager)

In particular, the problem this PR is fixing is visible in 2.21, not a new regression in 2.22.

Marking as draft to reflect this.

@huonw huonw marked this pull request as draft August 29, 2024 08:57
@benjyw
Copy link
Contributor

benjyw commented Aug 29, 2024

Sounds good.

@huonw huonw added the release-notes:not-required PR doesn't require mention in release notes label Sep 8, 2024
@huonw huonw marked this pull request as ready for review September 8, 2024 23:25
Copy link
Contributor

@huonw huonw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2.22.0 is out now

@huonw huonw merged commit 1fc38ef into 2.22.x Sep 9, 2024
25 checks passed
@huonw huonw deleted the cherry-pick-21361-to-2.22.x branch September 9, 2024 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bugfix Bug fixes for released features release-notes:not-required PR doesn't require mention in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants