x/ci-cd-pipeline-app-murano
Code Issues Proposed changes

Use FQN for naming packages which we upload

Browse Source 
Use FQN from manifest file, instead of hardcoded prefix.
Also adopt upload logic for new packages names.

Change-Id: If190bcddad3b0d310a51dc302303e86c202a41fe
This commit is contained in:
Sergey Kraynev 2016-08-12 15:42:29 +03:00
parent 3e6efbf84b
commit 66214e4abe
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
tools/prepare_packages.sh
View File

@ -131,7 +131,9 @@ if $build_packages ; then
# zip necessary apps
pushd "$source_dir"
for d in ${packages[*]}; do
filename="$destination_dir/org.openstack.ci_cd_pipeline_murano_app.$d.zip"
# get FQN for creating package
package_name="$(grep FullName "$d/package/manifest.yaml" | awk '{print $2}')"
filename="$destination_dir/$package_name.zip"
pushd "$d/package"
# check that file exist and remove it or create new version
if [ -f "$filename" ] ; then
@ -158,7 +160,8 @@ if $upload ; then
# to have ability upload one package independently we need to remove it
# via client and then upload it without updating its dependencies
for d in "${packages[@]}"; do
filename="$destination_dir/org.openstack.ci_cd_pipeline_murano_app.$d.zip"
package_name="$(ls "$destination_dir" | grep "$d")"
filename="$destination_dir/$package_name"
pkg_id=$(murano package-list --owned | grep "$d" | awk '{print $2}')
murano package-delete "$pkg_id"
murano package-import "$filename" --exists-action s