Always use exchangePublish.sh from the master branch
Add an optional arg to it which is the version number of the examples branch that should be cloned when publishing the examples to this Horizon exchange
If that arg isn’t specified, default it to: v and then the major and minor number of the hzn version, so in this case v2.27. I.e. the examples repo will follow the anax version (because that is the repo that has the most impact on whether an example is supported or not)
(In future cases where exchangePublish.sh can’t always be 100% backward compatible, it could have if-else statements within it based on the version number above.)
if the examples repo branch specified (or defaulted to) does not yet exist, it will print a warning and fall back to the master branch. This will allow our dev/test team to run the Post install doc page exactly as written, even before the branch exists, and as soon as we create the branch in the examples repo it will start using that.
if you set env var EXAMPLES_PREVIEW_MODE, the script will go thru the motions (clone the repo, switch to the branch, cd into each sample dir), but not actually publish anything into the exchange
i also added a new -X flag which will cause it to skip the publishing of services/patterns to the IBM org. This can be used when creating additional orgs in the multi-tenant case when you only need publish the sample deployment policies to the new org
exchangePublish.shfrom the master branchvand then the major and minor number of thehzn version, so in this casev2.27. I.e. the examples repo will follow the anax version (because that is the repo that has the most impact on whether an example is supported or not)exchangePublish.shcan’t always be 100% backward compatible, it could have if-else statements within it based on the version number above.)EXAMPLES_PREVIEW_MODE, the script will go thru the motions (clone the repo, switch to the branch, cd into each sample dir), but not actually publish anything into the exchange-Xflag which will cause it to skip the publishing of services/patterns to the IBM org. This can be used when creating additional orgs in the multi-tenant case when you only need publish the sample deployment policies to the new orgSigned-off-by: Bruce Potter bp@us.ibm.com