Uploaded image for project: 'Fabric'
  1. Fabric
  2. FAB-16206

External builder detect should not need to parse flags

    Details

      Description

      The first pass of the detect, compile, launch infrastructure was implemented with a collection of command line switches. This will become unwieldy over time as implementers will have difficulties ignoring unknown flags and parameters - especially flags that accept values.

      Instead we should remain consistent with the buildpack model that already exists - namely, we provide a list of directories that contain extracted files. If we need to provide more data, we can add an additional argument or populate additional files. This means that implementations should ignore extra arguments as a general rule until they know what they point to.

      detect should be provided a directory containing metadata.json (holding metdata as a basic map) and a reference to a directory containing the exploded source.

      Acceptance: external scripts do not need to process flags; existing parameters are reworked to fit this model.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                wlahti Will Lahti
                Reporter:
                sykesm Matthew Sykes
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Git Source Code