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

Register the python_aws_lambda_layer target type #19550

Merged
merged 1 commit into from
Aug 6, 2023

Conversation

huonw
Copy link
Contributor

@huonw huonw commented Aug 5, 2023

This ensures the python_aws_lambda_layer target type exists when activating the pants.backend.awslambda.python backend. This was missed from #19123, oops!

@huonw huonw added the category:internal CI, fixes for not-yet-released features, etc. label Aug 5, 2023
@huonw huonw requested a review from benjyw August 5, 2023 05:52
@huonw huonw merged commit fa5cf61 into pantsbuild:main Aug 6, 2023
25 checks passed
@huonw huonw deleted the bugfix/register-layers branch August 6, 2023 04:12
@benjyw benjyw mentioned this pull request Aug 7, 2023
huonw added a commit that referenced this pull request Aug 8, 2023
In yet more follow up to #19123 and #19550 for #18880, this ensures the
`PythonAwsLambdaLayerFieldSet` is part of the `PackageFieldSet` union,
so that `pants package path/to:some-layer` actually works.

I clearly didn't test this properly in #19123 or #19550, but now I have:
in a separate repo `PANTS_SOURCE=~/... pants package path/to:some-layer`
produces `dist/path.to/some-layer.zip`, with the expected contents. 🎉
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:internal CI, fixes for not-yet-released features, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants