AAP-40006 Empty docker directive on linting testenvs

[BrennanPaciorek]

linting testenvs do not need the database container

[AAP-40006] Do not create DB container on linting tox testenvs

Description

• What is being changed? overriding default docker directive on linting targets with an empty one
• Why is this change needed? Speed up lint targets
• How does this change address the issue? Not creating and starting a database to run black, flake8, or isort testenvs, which do not use the database container

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test update
• Refactoring (no functional changes)
• Development environment change
• Configuration change

Self-Review Checklist

• I have performed a self-review of my code
• I have added relevant comments to complex code sections
• I have updated documentation where needed
• I have considered the security impact of these changes
• I have considered performance implications
• I have thought about error handling and edge cases
• I have tested the changes in my local environment

Testing Instructions

Prerequisites

Fresh venv, if your working environment is old

Steps to Test

1. run tox -m lint

Expected Results

docker should not run as a result of this command

[john-westcott-iv]

Adding [HOLD] until the related JIRA makes it into a sprint.

[BrennanPaciorek]

Un-[HOLD]'ing

[BrennanPaciorek]

It seems these changes break tox -e <lint target> -- . not sure why though.

tox looks for a container . instead of treading . as a positional argument.

ValueError: Missing [docker:.] in tox.ini

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud