Metadata-Version: 2.1
Name: leverage
Version: 1.7.2
Summary: Binbash Leverage Command-Line tool.
Home-page: https://github.com/binbashar/leverage
Author: BinBash Inc
Author-email: leverage@binbash.com.ar
License: MIT License
Project-URL: Source Code, https://github.com/binbashar/leverage
Description: <a href="https://github.com/binbashar">
            <img src="https://raw.githubusercontent.com/binbashar/le-ref-architecture-doc/master/docs/assets/images/logos/binbash.png" width="250" align="left" alt="Binbash"/>
        </a>
        <a href="https://leverage.binbash.com.ar/">
            <img src="https://raw.githubusercontent.com/binbashar/le-ref-architecture-doc/master/docs/assets/images/logos/binbash-leverage.png" width="130" align="right" alt="Leverage"/>
        </a>
        <br clear="left"/>
        
        # Leverage CLI
        Leverage CLI is the tool used to manage and interact with any Leverage project.
        
        It transparently handles the most complex and error prone tasks that arise from working with a state-of-the-art infrastructure definition like our Leverage Reference Architecture. Leverage CLI uses a dockerized approach to encapsulate the tools needed to perform such tasks and to free the user from having to deal with the configuration and management of said tools.
        Provides the means to interact with your Leverage project and allows you to define custom tasks to run.
        
        
        ## Documentation
        For installation instructions and all documentation regarding Leverage CLI, please refer to [this page](https://leverage.binbash.com.ar/how-it-works/leverage-cli/).
        
        ## Running Tests
        To run unit tests, pytest is the tool of choice, and the required dependencies are available in the corresponding `dev-requirements.txt`.
        
        Integration tests are implemented using [bats](https://github.com/bats-core/bats-core/). Bear in mind that bats tests are meant to be run in a throwaway environment since they perform filesystem manipulations and installation and removal of packages, and the cleanup may not be completely thorough. As such, is highly recommended to run these tests using de docker image.
        
        ### Manually
        Unit tests:
        ```bash
        pip3 install -r dev-requirements.txt
        python3 -m pytest
        ```
        Integration tests:
        ```bash
        bats -r tests/bats
        ```
        ### Using docker image
        A Docker image suitable for running all tests can be crafted by running `make build-image`. After crafting the image all tests can be executed.
        
        To run all tests, run `make tests`. Alternatively `make test-unit` or `make test-int` for unit or integration tests respectively.
        
        ## Release Process
        * On every PR, a Github Action workflow is triggered to create/update a release draft.
        * The version number is determined by the labels of those PRs (major, minor, fix).
        * The release draft has to be manually published. This allows for any number of PR (features, fixes) to make the cut.
        * Once a release is published, another workflow is triggered to create and push the package to PyPi.
        
        
        ## Contributors/Contributing
        * Leverage CLI was initially based on Pynt: https://github.com/rags/pynt
        
        
        ## License
        Leverage CLI is licensed under [MIT license](http://opensource.org/licenses/MIT)[BinBash Inc](https://github.com/binbashar)
        
Keywords: BINBASH,LEVERAGE
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: Topic :: Software Development :: Build Tools
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Requires-Python: >=3.8
Description-Content-Type: text/markdown
