Thread: "soamdeploy add -a" option

OK I understand what "soamdeploy add -c consumer_ID" does, but there's also an option for "soamdeploy add -a appolication_profile_file".

What's the difference between the 2 in terms of functionality? I tried to look up in the symphony reference document, but there was no "-a" option for "soamdeploy add"

Usage:
soamdeploy add [-h] [-V]
soamdeploy add package_name -p package_file -a application_profile_file [-f] [-n] [-u user_name] [-x password]
soamdeploy add package_name -p package_file -c consumer_ID [-f] [-n] [-u user_name] [-x password]

Any ideas?

Good question CG.

If using "-a" option, soamdeploy obtains consumerId directly from the appliation profile where it is defined for the application, instead of having user typing it out if using the "-c" option. Otherwise there's no difference.

As for the reference guide. Yes, usage description for "-a" seems to be missing. I've appended this to the Known Issues with Symphony DE 4.0 Documentation thread.

Hope this helps.

I find -a more convenient, once made a type with -c ... ended up couldn't find the package when trying to register the app ...

There is infact mentioning of "-a" in the Symphony Reference Guide:

add package_name -p package_file -c consumer_ID
......

-c consumer_ID

Consumer for which to deploy the service packages. Only applications registered to this consumer can use the service packages.

The consumer ID must be a consumer leaf node, and must match the consumer ID specified in the application profile. Enclose the consumer ID in double quotes (" ") if it contains spaces.

Note:

For Symphony DE, -a application profile file name can be used instead of -c consumer_ID.

Just that -a wasn't listed under the Subcommand synopsis or any of the examples, so you missed it

Thanks for the clarifications. And Yes -a seems more convenient