bitovi / bitovi/bitops

Move boto3 from core to aws

Open
#254 0 comments 1 reaction 0 assignees View on GitHub
bug 🪲 complexity:easy enhancement ✨
Dominant language
Python
Stars
37
Forks
9
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
the [requirements.txt](https://github.com/bitovi/bitops/blob/main/requirements.txt) in the base contains `boto3` which is for AWS. That package installation should be moved to the [aws plugin](https://github.com/bitops-plugins/aws)

**To Reproduce**
Steps to reproduce the behavior:
1. check out the main branch
2. ensure no plugins in `bitops.config.yaml`
3. run a docker build (e.g. `docker build -t bitops:local .`)
4. Notice that `boto3` is being installed

**Expected behavior**
1. check out the main branch
2. ensure no plugins in `bitops.config.yaml`
3. run a docker build (e.g. `docker build -t bitops:local .`)
4. Notice that *no* `boto3` is being installed
5. Add the aws plugin
6. run a docker build again
7. Notice that `boto3` is being installed

Contributor guide

Open the contributing guide

Research direction

Start with requirements.txt and the Docker build described in the reproduction steps, then review how the aws plugin is added. Verify that a core build without plugins does not install boto3, while a build including the aws plugin does; confirm both scenarios with the provided docker build command.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker, python
Domain
build-system, cloud, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.