semvec/pypi-packages huggingface dataset:
osstrack 0.1.1.dev0
Manage uploads to osstrack.io.

# osstrack-action

GitHub action to upload your project dependencies to osstrack.io.

## Overview

This action allows you to upload your project dependencies to osstrack.io. It is a simple way to keep track of the dependencies of your project and to have various metrics about them like freshness, security, and licensing.

## Enabling the action

### Declare dependencies

To declare the dependencies of your project, you need to create a file named `.osstrack.conf` in the root of your repository. This file is managed by the osstrack utility and should not be modified manually.

```shellsession
$ cd <workspace>
$ pip install osstrack
$ osstrack add poetry.lock
$ # add a virtualenv where to capture the dependencies with pip freeze
$ osstrack add .tox/functional
$ # remove a dependency
$ osstrack del .tox/functional
```

### Sample Configuration

Defining Github Actions requires creating a directory `.github/workflows` inside your repository. Inside this directory, you create files processed when various events occur.

The simplest example of using this action would be to create the file `.github/workflows/push.yml` with the following contents:

```yaml
---
name: Push
on:
  push:
    branches:
      - main
jobs:
  osstrack:
    runs-on: ubuntu-latest
    steps:

      - name: Checkout code
        uses: actions/checkout@v4
      
      - name: Set up Python
        uses: actions/setup-python@v5
        with:
          python-version: '3.12'

      - name: Create the virtualenv
        run: |
          sudo pip install tox
          tox -e functional --notest

      - name: Upload dependencies to osstrack.io
        uses: osstrack/osstrack-action@0.1
        with:
          token: ${{ secrets.OSSTRACK_TOKEN }}
...
```

You need to store the `OSSTRACK_TOKEN` in the repository secrets. You can create a token in the osstrack.io website.

## Usage outside of a GitHub action

If you want to use the same dependency management in other CI pipelines or in a local test, you can install the python package:

```shellsession
$ pip install osstrack
```

Then you can use the `osstrack` command to upload the dependencies of a change:

```shellsession
$ cd <workspace>
$ export OSSTRACK_TOKEN=<your token>
$ # extract the dependencies of the current branch using tox
$ # or whatever you use to create the virtualenv
$ tox -e functional --notest
$ # Upload the dependencies of the current branch
$ osstrack upload
```

## Roadmap

- [ ] [](https://github.com/osstrack/osstrack-action/issues/)
network-builder 0.0.3
Infrastructure as code network builder
Requires Python: >=3.10

<p align="center">
  <img src="https://github.com/Levy-Y/Network-Builder/blob/main/assets/logo.png?raw=true" alt="Logo" width="35%"/>
</p>

# Network-Builder

[![Made with Python](https://img.shields.io/badge/Python->=3.8-blue?logo=python&logoColor=white)](https://python.org "Go to Python homepage") ![maintained - yes](https://img.shields.io/badge/maintained-yes-blue) ![Upload to PyPi](https://github.com/Levy-Y/Network-Builder/actions/workflows/publish-to-pypi.yml/badge.svg)

## Installation

### Using pip

```bash
pip install Network_Builder
```

### Manually
1. Download the latest release from the [releases tab](https://github.com/Levy-Y/Network-Builder/releases).
2. Install the wheel file using pip:

```bash
pip install /path/to/downloaded/wheel/file.whl
```

## Usage
```bash
python -m Network_Builder --config_file <file_path>
```

## Example config yml example:
```yaml
version: '1.0'

devices:
  - name: 'device1'
    type: 'cisco_ios'
    ip: '192.168.1.210'
    port: '22'
    username: 'admin'
    password: 'password'
  - name: 'device2'
    type: 'cisco_ios'
    ip: '192.168.1.211'
    port: '22'
    username: 'admin'
    password: 'password'

tasks:
  - name: 'task1 name'
    description: 'This is task 1'
    device: 'device1'
    commands:
      - 'show version'
      - 'show ip interface brief'
  - name: 'task2 name'
    description: 'This is task 2'
    device: 'device2'
    commands:
      - 'show version'
      - 'show ip interface brief'
```

## Contributing

We welcome contributions from the community. Before submitting a pull request, please ensure that:

- Your feature or bug fix is covered by tests.
- Your code adheres to the existing code style.
- You have added or updated documentation as necessary.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
gogogaga 4.0.1
All functions that assist in standardising development approaches.
Requires Python: >=3.6

# Structure of the functionality you are controlling

### Base objectives
1. Generate distribution files
2. Upload distribution files


### Behaviours
1. Generating distribution files
    - .tar.gz       -> Package source code (python code). Require compilation
    - .whl          -> Binary code

2. Generating


### Encapsulation objectives
1. Only generate one distribution file: Just generate the .whl file of the current version of the package
2. Upload a specific distribution file
    - Latest
    - Specified
3. Upload delete distribution file
    
### structure
1. Overarching container: .dist_management
2. distribution storage: .dist_management/dist_versions
3. distribution management configuration: .dist_management/config
    - setup.py
    - requirements.py




#### Operations
1. How to determine the latest specific distribution file?
    - Look at the version number 
2.