jesperkristensen / forcecmd Goto Github PK

You currently have to specify each individual file to be deployed on the command line. It should be possible to for example specify an entire group of components or do some kind of file name pattern matching, or integrate with git status.

The forcecmd.json file should be able to exclude parts you don't want, and it should be possible to select individual components to download on the command line.

Currently managed Appexchange packages are ignored.

It is currently not possible to deploy Folders because they don't have a file that corresponds to the -meta.xml file.

This dependency is quite large (304 KB) compared to what it would take to implement it ourselves.

For example if a custom settings field contains a password for an integration.

Currently all deployments are done without rollback on error, where a partial success will cause the successful components to be deployed. It should be possible to turn it on or off.

Seems you need to specify all the parts of a component as a unit when deploying.

We should write the status.json file in a nicely formatted way using multiple lines, so you can actually use the diff when version controlling the file.

In the Summer 14 release error messages are no longer shown in the deploy result. Can we work around this?

It is possible to query up to 3 components in a single list request.

We currently hardcode "ApexTriggerCoupling" and "WorkflowActionFlow" because the API claims they are supported, but using them cause API calls to fail. The Eclipse plugin works around this by making an individual list request for each type and mark it as unsupported if the request fails. We should consider doing something similar, but then we probably need to cache the result for performance.

It should be possible to retrieve data stored in custom settings, so we can put those under version control.