semvec/pypi-packages huggingface dataset:
trigger-informer-scan 0.2
Trigger scans in Informer via your CI/CD pipeline
Requires Python: >=3.6

Informer.io Scan Trigger Library

This library is designed to trigger scans in the Informer.io platform. It supports automated workflows by allowing users to initiate scans programmatically using an API key, an optional test UUID, and a list of assets.
Features

    API Key Authorization: Securely trigger scans using an API key.
    Optional Test UUID: Specify a test UUID for targeted scanning.
    Asset List Scanning: Initiate scans on a list of specified assets.
    Error Logging: Errors and failures are logged for troubleshooting, without halting execution.

Setting Up the Environment:

To use the library, you need to provide an API key. You can pass this as a command-line argument or set it as an environment variable.

export INFORMER_API_KEY=your-api-key

Triggering a Scan
1. Using Command-Line Arguments

You can pass the API key, an optional TEST_UUID, and a list of assets directly as arguments:

    triggerInformerScan --api_key your-api-key --assets "a.b.com,b.com,example.com"

Optionally, you can include a TEST_UUID. Scans will then start on both the assets in the test and the named assets:

    triggerInformerScan --api_key your-api-key --test_uuid your-test-uuid --assets "a.b.com,b.com,example.com"

2. Using Environment Variables

If INFORMER_API_KEY is set, you can trigger the scan by just providing the assets:

bash

    triggerInformerScan --assets "a.b.com,b.com,example.com"

And optionally the TEST_UUID:

    triggerInformerScan --test_uuid your-test-uuid --assets "a.b.com,b.com,example.com"

Limitations

    Frequency of Scans: Only one "once" scan can be triggered per 24-hour period per asset or test.
    Error Reporting: Errors are reported through logs and do not halt the script execution.

Finding the Test UUID

If you have a specific test in Informer.io for which you want to trigger a scan:

    Navigate to the test detail pane in the Informer.io platform.
    Locate the UUID, uniquely identifying each test.
    Use this UUID with the library for targeted scanning of related assets.
Flask-Classical 0.1.0
Flask extension for providing class-based views
Requires Python: >=3.10

# Flask-Classical

Flask extension for providing class-based views.

The following views are provided:
CreateView, EditView, DeleteView


## Installation

```bash
$ pip install Flask-Classical
```


## Usage

First create and initialize the `cbv` object:

```python
from flask_cbv import Cbv
cbv = Cbv(db, wtf)
# db is your Flask-Alchemist instance
# wtf is your Flask-Formist instance
```

And then you can add routes, for example:

```python
entries_blueprint.add_url_rule(
    "/<int:obj_id>/edit/",
    view_func=login_required(
        cbv.EditView.as_view(
            "edit_entry",
            form_cls=EntryForm,
            template="entries/edit_entry.html",
            obj_cls=Entry,
            blueprint="entries",
            validators=(current_user_is_author,),
        )
    ),
    methods=("GET", "POST"),
)
```


## License

`Flask-Classical` was created by Rafal Padkowski. It is licensed under the terms
of the MIT license.