Commits on Jan 16, 2020

1. Add support for choosing the package's release …

   Up until now, the appregistry-server always pulled the latest
   version of the requested packages, which makes sense for production,
   but not for testing and release phases of the packages.
   
   During testing, multiple version of the same package can be
   tested at the same time, and when releasing, it's not mandatory
   that the different releases will be released on the same date.
   
   When combining the appregistry-server logic, with the properties of the
   test and release phases, there is a need to create a complex automation
   for merging multiple versions (so they can be tested at the time) into
   a single bundle, and omitting non-ready releases from bundles,
   after testing and before the release.
   
   This change adds the possibility to specify the requested release after
   the package's name (e.g "Kubevirt:10.0.0"). If the version is not specified,
   the server will download the latest version from the appregistry.
   
   Signed-off-by: gbenhaim <galbh2@gmail.com>

   

   gbenhaim committed Jan 16, 2020
   Copy the full SHA

   d1948d7 View commit details

   Browse the repository at this point in the history