The `create` command will eventually have the following semantics. `create <RESOURCE> [PARENT_ID_1] [PARENT_ID_2]... <KEY> <VAL> <KEY> <VAL>` Some examples `epcc create customer email "test@test.com" name "John Smith"` `epcc create password-profiles 667d7853-9a71-490f-abed-8f0ef2f82541 name "Password authentication 2" username_format email` ### Acceptance Criteria For now because we don't have #3 working, we will only focus on top level resources, and not worry about how to do password profiles. 1. Calling `epcc create <X> key val` should post to `/v2/<X>` and using the code from #16 , post the JSON array as a body. 2. Any http error codes should be shown to the user, and return a non 2xx response should return non zero to the OS.
The
createcommand will eventually have the following semantics.create <RESOURCE> [PARENT_ID_1] [PARENT_ID_2]... <KEY> <VAL> <KEY> <VAL>Some examples
epcc create customer email "test@test.com" name "John Smith"epcc create password-profiles 667d7853-9a71-490f-abed-8f0ef2f82541 name "Password authentication 2" username_format emailAcceptance Criteria
For now because we don't have #3 working, we will only focus on top level resources, and not worry about how to do password profiles.
epcc create <X> key valshould post to/v2/<X>and using the code fromtest-jsoncommand support #16 , post the JSON array as a body.