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

Add support for supplying strip-components via buildpack.toml #183

Merged
merged 1 commit into from
May 28, 2021

Conversation

sambhav
Copy link
Contributor

@sambhav sambhav commented May 27, 2021

Summary

This PR adds a strip-components flag to postal’s service resolver. So that when it parses the buildpack tomls it can use artifacts that are tar’d in a slightly different manner. This would allow for customization of paketo forks that only have a different buildpack.toml.

For more details see https://paketobuildpacks.slack.com/archives/CULAS8ACD/p1619441959093300

Signed-off-by: Sambhav Kothari skothari44@bloomberg.net

Checklist

  • I have viewed, signed, and submitted the Contributor License Agreement.
  • I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
  • I have added an integration test, if necessary.
  • I have reviewed the styleguide for guidance on my code quality.
  • I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@sambhav sambhav requested a review from a team as a code owner May 27, 2021 17:00
@sophiewigmore
Copy link
Member

@samj1912 Besides that one nitpick comment I left, this looks great! I tried it locally and it works as expected. Cheers

This PR adds a strip-components flag to postal’s service resolver. So that when it parses the buildpack tomls it can use artifacts that are tar’d in a slightly different manner. This would allow for customization of paketo forks that only have a different buildpack.toml.

For more details see https://paketobuildpacks.slack.com/archives/CULAS8ACD/p1619441959093300

Signed-off-by: Sambhav Kothari <skothari44@bloomberg.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants