v1.1.0

This minor release extends the GUI functionality to the tapipy package, giving the users a much more streamlined and easy experience. Additionally, meta config management for the jupyterscinco package has been completed. Categories have been added to manage volume mounts and images for configs. Due to the tight coupling of the CLI to Tapis and tools such as tapipy, v1.1.0 release and all future releases will move in lock-step with every major and minor version change of those softwares.

New Features

• Dynamic GUI-like interface for the Tapipy package.
• Multiple methods for satisfying request bodies in the GUI (editor, prompt for each prop, and json file)
• JupyterSCINCO package for Meta config management

v1 Production release

This release sees a major architectural overhaul that makes tapisv3-cli not just a fully function command-line interface for the full suite of TACC Apis, but an extensible CLI framework upon which developers can easily add support for their own non-Tapis development workflows.

New Features

• Dynamic GUI-like interface that walks users through available commands and prompts them for the required inputs to satisfy those commands. Controllers that extend the BaseController class will come pre-furnished with GUI functionality.
• Multi-profile support so users can easily switch between users that have access to different resources and use different authentication methods.
• Core commands that assist developers in building their own packages based on templates simplifying the process of adding new functionality to the CLI
• Expanded help functionality
• Docker deployment option to run the CLI
• Before and After action filters for commands to house authentication logic, follow-up logic, etc
• Command aliases

Initial Release

This release allows users to consume the TapisV3 APIs from the command line. There are 2 methods by which this can be done.

The first is the TapipyController which maps command line arguments to TapisV3 Resources and their Operations defined in the TapisV3 OpenAPI spec Live Docs

The second is a set of user-defined controllers. These work in the same way as the TapipyController, but simply or shorten the syntax needed to perform the equivalent operations via the TapipyController. Additionally, user-defined controllers have complete control over how to handle querying of the APIs and how to render the results.