Add ability to specify manifest file for package-create command

Bug #1620981 reported by Sergey Kraynev on 2016-09-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-muranoclient
Wishlist
Unassigned

Bug Description

Currently "package-create" command provide ability to specify several option like:

  -n <DISPLAY_NAME>, --name <DISPLAY_NAME>
                        Display name of the Application in Catalog.
  -f <full-name>, --full-name <full-name>
                        Fully-qualified name of the Application in Catalog.
  -a <AUTHOR>, --author <AUTHOR>
                        Name of the publisher.
  --tags [<TAG1 TAG2> [<TAG1 TAG2> ...]]
                        A list of keywords connected to the application.
  -d <DESCRIPTION>, --description <DESCRIPTION>
                        Detailed description for the Application in Catalog.
  -o <PACKAGE_NAME>, --output <PACKAGE_NAME>
                        The name of the output file archive to save locally.
   --type TYPE Package type. Possible values: Application or Library.
  -l <LOGO>, --logo <LOGO>
                        Path to the package logo.

Most part of these options are already specified in manifest.yaml for package. And it's required file for creation new package.
Will be really useful to have ability specify existing manifest file instead of creation new one.

p.s. also IMO will be good to leave option to specify some other properties, which will overwrite some info in existing manifest

Changed in python-muranoclient:
status: New → Incomplete
Changed in python-muranoclient:
importance: Undecided → Wishlist
status: Incomplete → Confirmed
milestone: none → 0.12.0
Changed in python-muranoclient:
milestone: 0.12.0 → 1.0.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers