CLI support for Stored Procedures

PR #624 adds a feature for exposing Stored Procedures through REST APIs.

Links: Design Doc, RFC

A new option is required in CLI along with add command to be able to add a stored procedure.

The config file for declaring a stored procedure looks like below.

"GetBooks": {
      "source": {
        "type": "stored-procedure",
        "object": "get_books"
      },
      "rest": true,
      "graphql": false,
      "permissions": [
        {
          "role": "authenticated",
          "actions": [ "*" ]
        }
      ]
    },
    "GetBook": {
      "source": {
        "type": "stored-procedure",
        "object": "get_book_by_id"
      },
      "rest": true,
      "graphql": false,
      "permissions": [
        {
          "role": "authenticated",
          "actions": [ "*" ]
        }
      ]

As per RFC, this is the definition for the source field in a stored procedure

"type": {
    "type": "string",                                            
    "enum": [ "table", "view", "stored-procedure" ],
    "description": "Database object type"     
},
"object": {
    "type": "string",
    "description": "Database object name"
},
"parameters": {
    "type": "object",
    "description": "Dictionary of parameters and their values",

[Aniruddh25]

1. Do we support Paramerters and KeyFields? => Paramerters supported only when type is stored procedure, KeyFields supported otherwise - but not mandatory.
2. Is sourceName the only mandatory field? => if source is a string, then yes, that’s the only mandatory field. if its an object, both type and object are mandatory. The name property is actually called object in the schema. Please confirm with Davide about nomenclature.
3. An example of what values can KeyFields take? only array of strings? if yes can we change the type from Array to string[] => sure, in implementation we can do string[].

i feel like we should then remove --source

This is dangerous, we should make sure, CLI is backward compatible. No removals after releasing. We haven’t released publicly yet so we could be fine but lets keep in mind backward compatibility.

[abhishekkumams]

also, i feel like we should then remove --source, and have only one mandatory field --source.name. it will always take string as input.