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

pack should support pack extension package #1635

Closed
1 task done
natalieparellano opened this issue Feb 15, 2023 · 1 comment · Fixed by #1661
Closed
1 task done

pack should support pack extension package #1635

natalieparellano opened this issue Feb 15, 2023 · 1 comment · Fixed by #1661
Assignees
Labels
good first issue A good first issue to get started with. status/ready Issue ready to be worked on. type/enhancement Issue that requests a new feature or improvement.

Comments

@natalieparellano
Copy link
Member

Description

This is a sub-task of #1470

Just like we make buildpack packages, we should be able to make extension packages

Proposed solution

The command should work just like pack buildpack package, but with extensions:

Usage:
  pack buildpack package <name> --config <config-path> [flags]

Examples:
pack buildpack package my-buildpack --config ./package.toml
pack buildpack package my-buildpack.cnb --config ./package.toml --f file

Flags:
  -r, --buildpack-registry string   Buildpack Registry name
  -c, --config string               Path to package TOML config
  -f, --format string               Format to save package as ("image" or "file")
  -h, --help                        Help for 'package'
  -p, --path string                 Path to the Buildpack that needs to be packaged
      --publish                     Publish to registry (applies to "--format=image" only)
      --pull-policy string          Pull policy to use. Accepted values are always, never, and if-not-present. The default is always

Additional context

  • This feature should be documented somewhere
@natalieparellano natalieparellano added type/enhancement Issue that requests a new feature or improvement. good first issue A good first issue to get started with. status/ready Issue ready to be worked on. labels Feb 15, 2023
@itsdarshankumar
Copy link
Contributor

assign it please @natalieparellano

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue A good first issue to get started with. status/ready Issue ready to be worked on. type/enhancement Issue that requests a new feature or improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants