apitax 3.0.12
Brings together Commandtax, Scriptax, Standard Library, and the API to create a powerful automation framework. Please use StarterPack to quickly incorporate additional drivers, configuration, and custom code into Apitax.
Keywords: restful,api,commandtax,scriptax

# Apitax

Pronounced: *ahhp-ehh-tax*

**tl;dr: Code examples are at the very *bottom* of this documentation; however, I highly suggest you read through the documentation to learn what is possible.**

Finally, as Apitax features an exponential amount of various interactions, not all of them are documented here. Experiment with the syntax, Learn from the syntax, and Enjoy Apitax!

## What is it

Apitax is an API automation framework utilizing Commandtax and Scriptax. Commandtax is an API language which helps to quickly prototype powerful rest API requests. Scriptax is an automation language which utilizes Commandtax.

A more winded (and more detailed!) description called **Why use Apitax** is at the very bottom of this documentation.

## Builds and Installation

### StarterPack
I highly recommend you use the starter pack to get Apitax up and running. It provides you with a templated repository of files which you can change to better suit your application. 

The Apitax StarterPack can be found here: https://github.com/Apitax/StarterPack

StarterPack Benefits and Features:
* A complete set of working files to bring up Apitax with a single command
* Integrates Apitax/Core, Apitax/Drivers, Apitax/Scripts, and Apitax/CLI out of the box to give you a great experience
* Provides options to launch Apitax/Dashboard as well
* Completely customizable as if you were trying to use the raw Apitax code yourself
* Every service launches in Docker in one swift motion

##### Notes:
* StarterPack utilizes Pip and Docker to build the application. For this reason, an internet connection is required on the machine you use to build these images.

### Pip

Apitax on PyPi: https://pypi.org/project/apitax/

Using pip, you can bring in Apitax to your project.

### Docker
Docker is the recommended way to deploy Apitax. Please see the StarterPack for examples on how this can be achieved. While building Apitax yourself is possible, it is only recommended to do so if you are developing Apitax.

Warning: Apitax/Core is a base Apitax image. It is not meant to be deployed by itself, and must be used as a base for an application image which uses Apitax. Please see the StarterPack for more details. 

For the programmers out there: Think of the Apitax image as an `abstract class` in a programming language, and it is up to you to build the class that inheirits Apitax. 

#### DockerHub
* Apitax is available as an image on DockerHub: https://hub.docker.com/r/shawnclake/apitax/

#### Build yourself using Dockerfile
You can use the provided Docker file to quickly build an Apitax image. However, this image will not function correctly as it will be missing `config.txt`, `project.py`, and will have no drivers. Please see the StarterPack for more details on how this should all be included.

Steps:
* Clone the Apitax repository
* Build the image: `docker build --no-cache -t my-amazing-image .`
* Run the newly created image: `docker run -d -p 5080:5080 my-amazing-image`
    * This will run the container in the background, to run the container in the foreground remove the `-d` flag.

### Jenkins
* Jenkins is available here: https://openrubicon.com/blue/organizations/jenkins/Apitax/activity
* This address may change in the future
* Builds are not available on the Jenkins platform, and they likely never will be
* Builds are triggered periodically or via a Git Push
* Build artifacts will likely be pushed to a downloads server in the near future
    * Only non-dependency versions will be offered. On average, these are about 7.5% of the size of the versions which includes dependencies
    * Major and minor releases will also feature a dependency build, however bug and security releases will not feature a dependency version
    * It is best practice to always download the no-deps version and ensure you download the dependencies yourself

### Pip Packaging Instructions
* Use either Powershell or Bash
* Building the package: `python setup.py sdist bdist_wheel`
* Upload the package to Pypi: `twine upload dist/* -r pypi`
* More information can be found here: https://gist.github.com/ShawnClake/759e9d09af868ef18f8c7b39d1684ad4

### Readme Conversion Instructions
* Install `pandoc` if it is not already installed: `sudo apt-get install pandoc`
* Run the command: `pandoc -o readme.docx -f markdown -t docx README.md`

### Compile Antlr Grammar from another directory
This is sometimes necessary due to a bug in the antlr compiler with regards to paths
* Download the antlr compiler .jar file and save it somewhere.
* Inside of the directory where the .jar was saved, create the following folder hierarchy
    * build
    * src
    * scripts
    * logs
* Create a .bat or .sh file (dependent on OS) and add the following script:
``` bash
#!/bin/bash
grammardir=~/grammar
apitaxdir=~/apitax-dev/Apitax/apitax/grammar
antlr='antlr-4.7.1-complete.jar'
java -jar $grammardir/$antlr -Dlanguage=Python3 $grammardir/src/$2
java -jar $grammardir/$antlr  -lib $grammardir/src -o $grammardir/build -listener -visitor -Dlanguage=Python3 $grammardir/src/$1
cp -r $grammardir/build/* $apitaxdir/build
cp $grammardir/src/$2 $apitaxdir/src
cp $grammardir/src/$1 $apitaxdir/src
```
* Anytime you want to make changes to the grammar, do it from the new ~/grammar/src directory and run the script
    * You must pass in your parser and lexer grammars as arguments `bash ~/grammar/run.sh Ah210.g4 AhLex210.g4`

## Documentation and Usage

### Commandtax - Data Gathering, Manipulating, Usage
Commandtax is an efficient and fluent command language for Rest API's. Think of it as a better curl supporting better logging, better debugging, and more sensible flags.

#### Existing
* script \<pathToSomeScript\>
    * Sequences of commands to automate the execution of API requests
    * Scripts can include additional script commands which effectively means scripts can be nested
    * Scripts are run in order from top to bottom, if a nested script is found it executes the nested script before continuing through the current script
* custom \<someCustomCommand\>
    * Processes a custom request which is not baked into the utility
    * Parameters
        * --get : Uses a get method
        * --post : Uses a post method
        * --put : Uses a put method
        * --patch : Uses a patch method
        * --delete : Uses a delete method
        * --url : (string) The endpoint
        * --debug : Sets debug mode
        * --sensitive : Sets sensitive mode
        * --data-post : (json string) Any post data
        * --data-query : (json string) Any query parameters  ie. Endpoint.com/something?this=queryparam
        * --data-path : (json string) Any url path variables ie. Endpoint.com/users/{path_var}/show

#### Coming Soon
* shell \<someCommand\>
    * Runs the command in the shell and returns the response from the shell		
* An optional abreviated syntax for each command flag. These examples are subject to change
    * --get -> -g
    * --post -> -p
    * --put -> -q
    * --patch -> -w
    * --delete -> -e
    * --url -> -u
    * --debug -> -d
    * --sensitive -> -s
    * --data-post -> -z
    * --data-query -> -x
    * --data-path -> -c


### Scriptax - Control Flow, Scoping, and Automation
Scriptax is an API first automation language. Scriptax is not a general purpose language, instead it exists as a language tailored to optimizing automation in an API based environment.

#### Language
* `ct(required: "\<someCommand\>") {% %}`
    * Commandtax execution
    * A command is executed during the parsing of the line and its response is returned
    * Supports async, callbacks
* `get(required: "\<someCommand\>", optional: {dataObj}, optional: param1...n) {% %}`
    * Executes a get request
    * Data Object takes optional keys which correspond to Commandtax custom data: `post, query, path, header`
    * Returns the result
    * Supports async, callbacks
* `put(required: "\<someCommand\>", optional: {dataObj}, optional: param1...n) {% %}`
    * Executes a put request
    * Data Object takes optional keys which correspond to Commandtax custom data: `post, query, path, header`
    * Returns the result
    * Supports async, callbacks
* `patch(required: "\<someCommand\>", optional: {dataObj}, optional: param1...n) {% %}`
    * Executes a patch request
    * Data Object takes optional keys which correspond to Commandtax custom data: `post, query, path, header`
    * Returns the result
    * Supports async, callbacks
* `post(required: "\<someCommand\>", optional: {dataObj}, optional: param1...n) {% %}`
    * Executes a post request
    * Data Object takes optional keys which correspond to Commandtax custom data: `post, query, path, header`
    * Returns the result
    * Supports async, callbacks
* `delete(required: "\<someCommand\>", optional: {dataObj}, optional: param1...n) {% %}`
    * Executes a delete request
    * Data Object takes optional keys which correspond to Commandtax custom data: `post, query, path, header`
    * Returns the result
    * Supports async, callbacks
* {dataObj}
    * JSON object which includes optional arguments for the command such as:
        * auth - The set of credentials to use for this request
        * post - json - An object detailing any post parameters
        * query - json - An object detailing any query parameters
        * path - json - An object detailing any path parameters
        * driver - The driver to use for this request
        * strict - default: true - Whether or not the entire script should fail if the requests returns a status code >299 or <200
* `new OpenstackNetworks(optional=parameters);`
    * Creates a new instance of the OpenstackNetworks script
    * The optional parameters should correspond to the sig line
* `\<attributes\> \<methodName\>(optional=parameters) {}`
    * Adds a method to the current script
    * Attributes can be either `api` or `script`
* `\<methodName\>(optional=parameters);`
    * Executes a method with the optional parameters
* `async`
    * Add this keyword in front of any keyword which supports async to run the operation in a new thread
    * Can also be used in front of a method statement: `api async getNetworks() { }`
    * `async get("http://placeholderjson.com/users", {}) {% %}`
    * `someVar = async get("http://placeholderjson.com/users", {}) {% %}`
    * Callbacks execute prior to storing the result of the request into a variable
    * Variable will be initialized with a new thread instance and once the thread completes it will be replaced with the result as returned via the callback
* `await \<someOptionalVar\>;`
    * When a variable is specified, wait until the async execution specified by that variable completes.
    * When no variable is specified, wait until all of the open threads in the current script complete before moving on
    * Can also be used when using a method call: `result = await openstack.getNetworks();`
* {% %};
    * Callback block
    * The contents will be executed in an isolated scope, usually only having access to a `results` variable
* `str()`
    * Cast to string
* `int()`
    * Cast to rounded integer
* `dec()`
    * Cast to float
* `bool()`
    * Cast to true/false
* `list()`
    * Cast to list
    * Only works on strings
* `dict()`
    * Cast to dictionary
    * Works on lists, strings, ints, decs
* `\#`
    * Return the length of the variable
    * Works on strings, lists, dictionaries (Only returns the top level count)
* `\$`
    * Escapes the label name such that labels which are the same as language keywords can be used
* `\!`
    * When adding this to the very start of a statement, the execution of that line will not be logged or printed
* `\@`
    * Returns the reflection of a variable
* `extends(\<someScriptPath\>);`
    * Adds polymorphism to the script by extending another script
* `del(\<someVar\>)`
    * Remove someVar from the current scope
* `return \<optionalVar\>`
    * Exits the script immediately and returns some expression
* `options(optional=parameters)`
    * Used to specify options for the script
* `sig(param1Required, thisParam=isOptional, thisOneisRequired);`
    * Specify parameters for a script
* `if (condition) {}`
    * IF statement
* `while (condition) {}`
    * While loop
* `for \<someVar\> in \<existingVar\> {}`
    * Loop through each item in a list in order
* `for \<someVar\> in \<someNumber\> {}`
    * Loop from 1 to someNumber and set someVar to the current iteration
* `each \<someList\> {% %};`
    * Loop through a list setting `results` to the current item and executing instructions in an isolated callback
* `\<someVar\> = \<someExpression\>`
    * Sets a variable
    * Supports expressions, strings, numbers, booleans, dictionaries, lists, and commandtax responses
* `"this is a string {{ someVar }}"`
    * Injects the contents of a variable
    * Fancy stuff is possible such as: set newVar = ct("{{someVar}}")
* `\< someExpression \>`
    * Injects the expression
    * In this case, the arrow brackets must be included
* `from driverName import someScript as someName`
    * This imports other scriptax to be used inside of the current script
    * `from` and `as` are optional
* `auth(\<someAuthObject\>)`
    * Sets the default auth for the current executing script
* `login(username={{someUser}}, password={{somePass}}, token={{someToken}}, driver={{someDriver}}, extra={{someJSONObj}})`
    * Each parameter in login is optional. The required parameters is defined via the driver to be used by the login command. This driver is either the default script driver or the driver specified in the login parameters.
    * Returns an auth object
    * Can be used directly with `auth` such as: `auth login(username=test, password=test123);`
* `endpoint(someEndpointName@someDriver)`
    * Using the drivers `getCatalog` method, this will return the the endpoint found in the catalog of the specified driver
    * This can be used directly with `url` such as: `url endpoint('keystone@openstack')`
* `url(\<someUrl\>)`
    * Sets the current working URL to be used in further commandtax
* `log("log some output to the console & log file")`
    * Supports expressions
* `// some comment`
    * Inline comment
* `/* some comment spanning multiple lines */`
    * Block comment

#### Scopes
In Scriptax, there is no global scope. Every piece of data belongs to a scope. There are many different scope types within Scriptax:
* Script Scope - These are symbols that are accessible within an entire script. Examples of these are sig parameters or script level variables.
* Method Scope - These are symbols that are accessible from within a method. Of course, this scope inherits from the script scope.
* Flow/Block Scope - These are symbols that are accessible within a flow block such as if statements or loops. Of course, this scope inherits from the script scope.
* Callback Scope - These are symbols that are accessible within a callback. Usually, a `result` variable will be accessible as well as any other values passed in via `(optional=parameter) -> {% %}` syntax. Typically callback scope is read only and any changes made to any variables in here will only be changed within the callback scope. The only exception to this is the `result` variable which is generally used to pass data back in a return style. 

`Script`, `Method`, and `Flow/Block` scopes will all inherit their parent scopes. `Callback` scopes on the other hand are completely isolated and must be told explicilty which symbols are allowed in and they will only be allowed in as read-only.

#### Architecture
* In Scriptax, every file is considered an object. In other words, every file is analogous to `class` in other programming and scripting languages. 
* Instances in Scriptax only ensure that variables in the script scope are unique. 
* Methods in Scriptax are inherently `static`. In other words, methods are not unique per instance and can be called on the script itself or on a script instance. If a method is called via the script itself and attempts to utilize script scope variables, an error will be thrown.

#### Structure
Scriptax has a structure which must be followed or else errors will be thrown or the script will complete with errors.

The first few lines of a script are dedicated to `global_statements`. These statements include `extends`, `signature`, `options`, and finally `imports`. Scriptax is extremely strict when it comes to `global_statements` and thus they must even be in order. If you choose to use `extends` it must be the first statement in the file with no exceptions. If you choose to use `signature` it must come immediatly after `extends`, but if you aren't using `extends` then `signature` must be the first statement within the file, so on and so forth. The order of `global_statements` is as follows:

1. `extends`
2. `signature`
3. `options`
4. `imports`

While `extends`, `signature`, and `options` should only ever occur 0 or 1 times within a script file, `imports` can occur 0..n times within a file. 

After the `global_statements` feel free to use any non global statements as you see fit. 

#### Scriptax Gotchas/Tips/Tricks
* Accessing parameters as defined by `sig` should be done like so: `param.firstParam` where `firstParam` is the name of the parameter
* For best compatbility with Apitax/Dashboard and Apitax/CLI, please start each Scriptax file with a `sig` line if nessecary. 
* You can use arrays via dot notation
    * set someVar.1 = num1
    * set someVar.2 = num2
    * set someVar.\<counter\> = num3
    * When doing this, the first usage of a variable must either be someVar = "{}" or an index as part of that object. Failure to do this will result in errors being thrown.

#### Best Practices
* End each script with `await;` to ensure all async requests are completed before it returns to the parent script.
    * Ending with `await;` followed by `return \<someVar\>;` is also acceptable
* Delete unused variables from the root scope when they are no longer needed `del \<someVar\>` 
* Only export/return necessary variables from subscripts
* Keep the root scope as clean as possible
* Scripts should be small, containerized pieces of code that strictly follow SRP.
     * Think of Scripts as lego blocks, eventually you can put a bunch of them together to build something really cool
* Scriptax is a flexible, forgiving, and powerful language
    * Play around to see what you can and cannot do. There are too many edge cases to list explicitly.

#### Coming Soon
* A time method

### Commandline Interface (CLI)
* You can activate Apitax from the CLI directly without needing a wrapper package
* Run the tests.py file found in the root Apitax directory, and supply the following arguments
    * --cli : (Optional) Quickly select CLI mode
    * --api : (Optional) Quickly select web server mode
    * --debug : (Optional) Output the request response status, headers, and body
    * -u <input> : (Optional) Specify the authentication username - Only applicable in CLI mode
    * -p : (Optional) Ask for password input right away. If -u is specified, but this is not, the application will ask for a new set of credentials for authentication. But, it will use the -u value for any username fields within further requests. This allows someone to authenticate as admin, but run commands applicable to another user.
    * -r <Input> : (Optional) The request - Only applicable in CLI mode
    * -s <input> : (Optional) Run a script of requests specified by the file path <input>, authentication for all of these requests are specified by -u & -p

### Modes
* CLI : Make a request from the command line
* API : Start the api server

### Configuration
* An example configuration file is stored in the root of the repo

### Supported Authentication
* Authentication is prebuilt for HTTP Basic and Token based authentication
* Authentication is largely left up to a developer in custom scenarios
    * Driver files facilitate this requirement

### Drivers and Plugins
** This has been redone and requires updated configuration **
* Drivers and plugins are used to extend the functionality of Apitax to an arbitrary API
* Drivers must be dynammically added to the application via the `project.py` file. Please see Apitax/StarterPack for an example of how this can be done.

### Examples of Apitax in Action:

#### Commandtax Examples
```
custom --get --url <someEndpoint>
custom --get --url <someEndpoint> --data-param '{"is_domain": true}'
custom --post --url <someEndpoint> --data-post '{"title": "im the title"}'
custom --put --url <someEndpoint> 
custom --patch --url <someEndpoint>
custom --delete --url <someEndpoint> 
custom --get --url <someEndpoint> --data-param '{"user.id": "1"}'
custom --get --url <someEndpoint>/with/some/{ohyear}/url/params/{981} --data-param '{"is_domain": true}' --data-path '{"ohyeah":"no", "981": "yes"}'
```
`script ~/path/to/my/script.ah`

#### Scriptax Examples

```
// async-tests.ah

url "https://jsonplaceholder.typicode.com";

bob = [];
threads = [];

/*each get("/users", {})
{%
	url "https://jsonplaceholder.typicode.com";
	threads[] = async get("/posts", {
          	"query": {
                "userId": result.id,
            },
        }) {%
        	log("The user has these posts: " + result);    
        %};
%};*/

for user in get("/users", {})
    threads[] = async get("/posts", {
            "query": {
                "userId": user.id,
            },
        }) {%
        log("The user has these posts: " + result);
        //bob[] = result;
    %};

await threads;

del threads;

script("apitax/grammar/scripts/base.ah");

log("yo man im at the end");


/*for user in get("/users", {})
    threads = async get("/posts", {
            "query": {
                "userId": user.id,
            },
        }) {%
        log("The user has these posts: " + result);
        bob[] = result
    %};

//bob[] = "hey";

for t in threads
	await t;

log(bob);

log("Im quite confused");*/

```

```
// base.ah

url "https://jsonplaceholder.typicode.com";
for user in get("/users")
{
    /*result = get("/posts", {
        "query": {
            "userId": user.id,
        }
    });
    log("The user has these posts: " + result);*/

    log("the user has ID: " + user.id);

    async get("/posts", {
            "query": {
                "userId": user.id,
            }
        }) {%
        log("The user has these posts: " + result);
    %};

}  

response = post("/posts", {
    "post": {
        "title":'foo',
        "body":'bar',
        "userId":1
    }
});

log(script("apitax/grammar/scripts/jen.ah", {}, "i am parameter 1", "i am parameter 2"));

//response = ;

log("Please " + ct("tests my script", {}, "i should be a parameter"));


testlist = ["one", "two", 'three', ["a", 'b', 'c', 'd'], {"test": "failed", "yes": "no"}];

log(#testlist.0);


/*async ct("some command execution")
{
log("some integrated callback");
}

async ct("some command execution");

status = async ct("some command execution");

await status;

status = [firstAsync, secondAsync];
await status;

async bobo in get("/users")
{
    log("Async callback: " + bobo);
}*/

async get("/users");



somelabel = async get("/users")
{%
    log("I am an optional callback");
%};
//anotherRequest0 = async get("/users");
//anotherRequest1 = async get("/users");
//anotherRequest2 = async get("/users");

await somelabel;

log("i am that label" + somelabel);


get("/users") {%

log(result);

%};

async get("/users") {%

log(result);

%};


for iter in 10 {

    async get("/posts", {
            "query": {
                "userId": iter,
            }
        }) {%
        log("The user has these posts: " + result);
    %};

}

log("here is where the magic happens");

get("/posts", {
        "query": {
            "userId": 5,
        }
    }) {%
    log("The user has these posts: " + result);
%};


await;

```

```
// jen.ah

options dict('{"params": ["name", "game"]}');
answer=2+2;
name "quinn";

set qwer = "im in jens script";


export qwer;

//export ct("script apitax/grammar/scripts/shawn.ah");

set iam.hope.this.works = ct("custom --get --url https://jsonplaceholder.typicode.com/users");

export iam;

set test = "hello";

//return '{"cool": "beans"}';

log(params.passed.0);

log(params.passed.1);

log(params.name);

log(params.game);

log(2+2);

return params.passed.1;

//return "test";


await;

```

```
// my_script.ah


options dict('{"params": ["first"]}');

log("I got here");

log(params.first);

return "work";


await;

```


## Why use Apitax
Let's presume that a backend exists only as an entity that does nothing until it is told to do something.

If this is the case let's also assume there will be no interface into the backend other than a RESTful API. 

Okay, so let's say we want to build a frontend that will list every user's 10 most recent posts. 

One way we can do this is to make an API request to retrieve a list of our users. Then, in JavaScript, we can loop through that list of users, and for each one we can make an API request to get their most recent posts. In Javascript, we can then compile this list of users together and display it. 

Sounds simple - except how do we then speed up this process by utilizing asynchronous code. We begin to introduce all sorts of nested callbacks, desync's in our JavaScript that are complex to sort out, difficult bug testing, and we start to break DRY as we copy bits and pieces of this code to different files/pages to list different types of data in different ways.

We can solve some of our DRY problems by creating giant API classes that have helper methods for each of these types of calls, but it will still become quite a mess.

What we want is to focus on frontend development - not the API request garbage. By doing this, we are enforcing SRP of the frontend architecture as a whole. The bulk of the frontend code should be dedicated to displaying data, getting input, and showing users responses from their input. It should not be thousands of lines of us making API calls and trying to organize the data. There has to be a simpler way, right?

What if the frontend only had 4 different API requests to make. 1 for authentication, 1 for getting a catalog of endpoints, 1 for getting the status of the system, and finally 1 to facilitate the transfer of bidirectional data. Here is where Apitax/Commandtax comes into play. We now have a single endpoint to send a request to, and that request's payload is commandtax. 

Great! Now, instead of a bunch of helper methods all over the place, now we might just have some helper string constants that store frequently used commands. Already much cleaner and more workable. But, this still doesn't solve our DRY problem, SRP, or the callback and desync hell we will face from having to make several requests in a row to accomplish a task.

Enter: Scriptax. Now, any of us can create little self-contained sub module files which do these sequential requests for you. These files are called Scripts. One script might have the responsibility of getting a list of users that follows some set of parameters, and another might call that users script and then using the response returned, it could get a list of posts for each of those users and return them. 

Okay, now our frontend only has 1 short line of commandtax which is executing a script. If the scripts are written well, there is no more callback hell, SRP is preserved, DRY is enforced, and the data returned to us will already be in a very workable format. Kaboomskies, you just saved yourself 2 dozen lines of hard to debug JavaScript, and instead, it's a one liner that returns the data already in a workable format


=======
Brings together Commandtax, Scriptax, Standard Library, and the API to create a powerful automation framework. Please use StarterPack to quickly incorporate additional drivers, configuration, and custom code into Apitax.