tree 3938b77c0d362272d75212f44d666396ec2fc04e
parent 42b72dbd6ea34753a43b3dd89ffff2520a978099
author Ignas Anikevicius <ignas.anikevicius@woven-planet.global> 1689009549 +0900
committer GitHub <noreply@github.com> 1689009549 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkrD2dCRBK7hj4Ov3rIwAAErwIACfPTciLc/bsH6f4IHC9O9dw
 hNy/1Ds4E7+mygRkCeR9oqxlfXKo8iW4xZEr/QT1YTjwvx36VqjpQ0vwkngGOlhU
 E9/FAfPSF0wEXNZtjljni2iwTS0zubjGBHfPbuYESOtndsI/7ELg7VyeHj5R+cQp
 ja6tRq+aRaiKtwytaBCrVQsvDbtdPzj3Wr6MTH7ZJRJYrfG3VZwbucYG9fvnmKRD
 A2cYIN8P4PBhuW7WKGRbpQH2ojDONP69bFlaRQ8SA89gXm1lImIpPPgljF5NUryN
 NQAA5kDZCgQKhhW0oD05SexGS23slucB/kbqgp+vJBB3XLHK9YZMelOrcJPxSzI=
 =vfrE
 -----END PGP SIGNATURE-----
 

feat(gazelle): support multiple requirements files in manifest generation (#1301)

For certain workflows it is useful to calculate the integrity hash of
the manifest file based on a number of requirements files. The
requirements locking is usually done by executing a script on each
platform and having gazelle manifest generator be aware that more than
one requirements file may affect the outcome (e.g. the wheels that get
passed to modules map may come from multi_pip_parse rule) is generally
useful.

This change modifies the generation macro to concatenate the
requirements
files into one before passing it to the manifest generator.