this method should work.
another option, if this is more of a one time thing (where you don't need the files stored in bladelogic) would be to write an nsh script that takes parameters and they uses dsync or just cp to copy the files from one server to another based on the parameters.
then you could have some blcli that just creates new nsh script jobs w/ the right parameters and runs them.
there should be some examples of package creation in the blcli help docs if you look in the BlPackage name space area.
Thanks for you comments Bill.
I thought about using nsh script for these scenarios but if we use nsh script; how can we rollback if we need to? One of the reasons that I intend to use BlPackage is for rollback if we need to.
Do you have any example or tell me how to create BlPackage from Live Server objects using blcli scripts.
yeah - if you need rollback use a blpackage, but in that case, you probably don't want to use the zip, you want to add all the files directly into the package.
for the blcli you need something like
BlPackage createPackageFromAsset - do you have access to the blcli help docs? you really just need to dig though there to figure out the commands - the naming is pretty good in most cases.
using that command, you'd need a component template created first that lists all of the files or directories you'd want in your package, kind of like a shopping list...
I will have to remember to add all files to the package instead of a zip file.
I do have access to blcli help docs and will dig into it.
If I'm using post-commands to move files where they need to be moved on target server. Does this effect the rollback process? If so, what is the alternative method?
if you define post undo commands that will really undo your changes, then rollback will work.