Specifying a properties file on the command line would be a good way to get going, especially when another jclouds application like Whirr can use the same file.
Skeleton configs for different clouds could show what props are necessary. For instance, it is unclear how TenantID in HPCloud maps to the current credential commandline flags. It also helps if people know what the prop values look like for each cloud so that jclouds-cli can help them get going when they are just learning a new cloud even though terminology differs between clouds.
Specifying a properties file on the command line would be a good way to get going, especially when another jclouds application like Whirr can use the same file.
Skeleton configs for different clouds could show what props are necessary. For instance, it is unclear how TenantID in HPCloud maps to the current credential commandline flags. It also helps if people know what the prop values look like for each cloud so that jclouds-cli can help them get going when they are just learning a new cloud even though terminology differs between clouds.