CLI: Store credentials by id and map to UUIDs on deploy

[josephjclark]

• save credentials by id (not uuid) in the steps
• In the state file, under the credentials array , we are given all assocaited credentiasl with a name, email and uuid
• At deploy time, we convert the credential name into a UUID, and post that

This makes credentials much much more portable

What do we do if the UUID cannot be mapped?

Maybe the provisioner can create an empty credential to be filled in by the user. Or it can look up a matching credential by id.

If the credential exists, a new relationship will be created with its own UUID.

[josephjclark]

Should this be configuration or credential internally? Do we add a new key to the workflow structure or iare we just swapping out the UUID?

How does this affect the credential map? The credential map should use the id now right? Not the uuid

If we update the credential map to use ids, not uuids, then we keep step.configuration as a string. That string tells the CLI to load from a map - that's all. So we don't need a special key on workflow json here

What about the project class? Should that save credential or configuration?