Re: On boarding of a new CF system build pack for Rust
|
Borrmann, Andre
Hi Dan,
thanks for your reply. While a custom/community buildpack is a viable option my question is more related to an enterprise context. Which means, building enterprise applications and deploy them to CF. This would require reproducible build steps and thus should not be dependent on external hosted buildpacks. So either we would require the custom buildpack to be hosted within our enterprise boundaries or – the preferred option – being part of the CF stack itself, like JAVA buildpack, GO buildpack etc. (so it should be best listed here: https://docs.cloudfoundry.org/buildpacks/system-buildpacks.html).
This kind of lead to the question how those buildpaks became system build packs and how could Rust become a part of this party. Where should this being requested and who would be responsible to get this “onboarding” kicked off.
Thanks in advance.
BR André
From: <cf-dev@...> on behalf of Daniel Mikusa <dmikusa@...>
Hi,
Not sure this exactly answers your question. I am also Rust fan and so a while back felt compelled to write a set of Cloud Native buildpacks (v3 buildpack) for Rust & contributed it to the Paketo community (Paketo is a CF Foundation project for implementations of the v3 cloud native buildpack spec).
I haven't tried it, but I'm pretty sure you could `pack build` images with this buildpack and `cf push -o` them onto CF. It's one extra step, but it should work.
Maybe there'd be a way to retrofit it to work as a v2 CF buildpack? I think some folks were working on a wrapper a while back.
Dan
|
|
|