Skip to content

create support (With Resource Types) #43

@steve-r-west

Description

@steve-r-west

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

In #20 we added support for create without actually knowing anything about resources. But now with #3 we should be able to support resources.

Acceptance Criteria

1.When you call epcc create <X> a b c d , the resource should be looked up, and arguments a,b,c,d should be consumed to fill in the required variables for the URL path for parent resources. (e.g., a customers would consume 0 because it has no parent resources, but epcc create customer-address would consume a because a would be treated as the customer id.
* The everything that is not used as an ID should be used to create a JSON body like in #16 .
2. Any http error codes should be logged to the user, and a non 2xx response should return no zero to the OS.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions