---
# System prepended metadata

title: Untitled

---


## Package Authoring:


$> pacMan create pkg:

1. What is the intention here(a. pkgCreate b. pkgUpdate etc):
2. Enter the pkg Name:
3. Enter the pkg Verison:(default: 1.0.0)
4. Enter from where to fetch the pkg data e.g. (imgpkg, helm, inline etc):
    
    a. Based on above, ask the details:
    
        a.a. If option selected is imgpkg, then ask Do you want to create the imgpkg bundle first(y/n):
    
        If Yes,

            a. Enter the source of truth(github, hg, http etc.):

            b. Based on source of truth, ask the details:

            c. Will this be templated via ytt(y/n):

                1. Enter ytt overlay file Location

                2. Enter ytt values file locaiton
            d. Do you intend to push it to registry(y/n):

                If yes:

                1. Enter the registry details.
5. Enter the Release Notes(default: Release notes for {pkgName}:{pkgVersion}): 
6. Enter the License(default: Mozilla):
7. Enter the Capacity Requirement:(default: "RAM: 1GB, CPU: 1")
8. Enter the namespace for the pkg(default: default):
9. Enter how do you wish to template(helmTemplate, ytt etc.):
    
        a. Based on above, ask the details:

10. Enter the valueSchema(This needs more discussion- should we accept it single by single, we generate automatically, we accept file etc.):

11. Enter how you want to deploy it(kapp, kubectl):
    
        a. If kapp, ask for any cli paramters to be passed as an array:



$> pacMan create pkgMetadata:
1. Enter the name
2. Enter the namespace
3. Enter the Description about pkg(default: pkgName):
4. Enter the LongName(default: pkgName):
5. Enter the ShortName(default: pkgName):
6. Enter the maintainers(default: host name):
7. Enter the icon Image(default: Carvel Image):
8. Enter the provider name(default: hostname):
9. Enter the Categories: 
10. Enter the support Description: 

### Few Notes:

* As mentioned in the meeting, we can have `lite` and `full` passed as CLI parameter if we really dont want the first time user to press so many enters.

* In this flow, encapsulated the bundle creation under step 4. If user selects option `imgpkg`, then it means he knows about it and it is ok to ask these questions. e.g. first time user can select github, helm (basically, anything except imgpkg) and user will be by passing the whole bundle creation step.





1. Input a:
Why this input ?
Based on input a, what are the cmds will run, show what is happening, wht is the o/p
2. Enter which pkgType you are interested in:
Why this input ?
Based on input a, what are the cmds will run, wht is the o/p