Rob Dimsdale-Zucker

@tsusadivyago as you mentioned, there are only really two options to achieve this: 1. Adding the terraform binary to a custom stack. This will require you maintaining your own stack....

Concretely, to add a binary to an existing stack I would do the following: 1. clone the stack repo in question (e.g. `jammy-full-stack`) 2. parse the `stack.toml` file with a...

The @paketo-buildpacks/go-maintainers had quorum and reached a majority consensus on moving this forward. We agreed to start with the absolute simplest solution - described above - and defer any configuration...

The last couple of tests have failed due to a mismatch in layers. This is flaky, as re-running it seems to result in it passing. Example output: ``` === CONT...

Flaky reproducible builds test (we've seen this before). Re-running. ``` === CONT TestIntegration/Integration/Reproducible_Builds/building_a_PHP_app_that_contains_vendored_Composer_packages/creates_a_two_identical_images_from_the_same_input reproducible_builds_test.go:134: Expected : "...a[256](https://github.com/paketo-buildpacks/php/actions/runs/4563657034/jobs/8052426440#step:5:257):aa3aac..." to equal | : "...a256:d60502..." ```

Test failure - possibly a race condition in the tests. Re-running. ``` === NAME TestIntegration/Integration/Reproducible_Builds/building_a_PHP_app_that_contains_vendored_Composer_packages/creates_a_two_identical_images_from_the_same_input reproducible_builds_test.go:134: Expected : "...a256:d0c407..." to equal | : "...a256:f157dc..." ```

@ryanmoran if the `cpython` buildpack is optional, which buildpack (if any) in nodejs build order would require it, and under what conditions? It seems like we'd need to define both...

``` panic: could not unmarshall tags: json: cannot unmarshal object into Go value of type []main.GithubTagReponse ``` Most likely a `403` that we don't check the error code for. Flake...

Just to add some additional context - this is probably not a "network flake" but is more likely a rate limit due to lack of authentication when calling GitHub's API.

This is the same `403` from not using authentication. Subsequent run succeeded.