Skip to content

2.1.0
Compare
Choose a tag to compare
@NelsonVides NelsonVides released this 19 Aug 10:41
· 245 commits to master since this release
2.1.0
b4b4ab2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

2.1.0 - 2020-08-19

This release focuses on the REST API, which is now powered by OpenAPI Specifications generated by openapi-generator.

The main changes:

  • PR#123 - simplification of scenario uploading, now it can be done using the following command: curl -s -H "Content-Type: text/plain" -T scenario.erl 'http://localhost:4000/upload'
  • PR#124 - switch from cowboy-swagger to amoc_rest (framework generated using openapi-generator). Online Swagger UI documentation for the current release can be found here.
  • PR#125 - possibility to update scenario settings at runtime. Support of the settings for helper modules. Update of the -required_variable(...) module attribute format:
-type module_attribute() :: #{name := name(),
                              description := string(),
                              default_value => value(),
                              verification => verification_method(),
                              update => update_method()}.
  • PR#130 - added new /scenarios/info/{scenario_name} REST API, it returns edoc description of the scenario module and all the relevant settings declared using -required_variable(...) attribute.
  • PR#131 - implementation of the /execution/* REST APIs:
    • /execution/start - starts scenario on all the nodes in the cluster
    • /execution/stop - stops scenario execution on all the nodes in the cluster
    • /execution/add_users - adds new users on all or specific nodes in the cluster
    • /execution/remove_users - removes users on all or specific nodes in the cluster
    • /execution/update_settings - updates scenario settings on all or specific nodes in the cluster
  • PR#132 - remove the legacy way of providing configuration through erlang app environment variables
  • PR#133 - significant improvement of the /status REST API, introduction of the /status/{node_name} REST API (which can be used to check the status of other nodes in the cluster). The following thing are reported:
    • Amoc application status (up/down)
    • Amoc specific env. variables
    • Amoc controller status + runtime scenario settings for running/terminating/finished states
Assets 2
Loading