FEAT: PyRIT Config by ValbuenaVC · Pull Request #1343 · Azure/PyRIT

ValbuenaVC · 2026-01-31T00:54:38Z

Description

Adds a config as ~/.pyrit_conf (~/.pyrit_conf_example included in repo) which can be loaded in by a new ConfigurationLoader to both make initializing pyrit less verbose and also parameterize pyrit the same way across the CLI and GUI. Configuration file support for the CLI tools enables more complex setups that were not possible or cumbersome previously. New features:

Initializers with arguments specified in the config file, which was not possible previously with the CLI
Configuration file with same fields as our initialize_pyrit_async method(s)
Auto-loading of config file if it exists
Config precedence (default config file < explicit config file < individual CLI args)

Tests and Documentation

Added as tests/unit/setup/test_configuration_loader.py.

romanlutz · 2026-02-05T18:45:45Z

pyrit/cli/frontend_core.py

        initializer_names: Optional[list[str]] = None,
        env_files: Optional[list[Path]] = None,
-        log_level: str = "WARNING",
+        log_level: Optional[str] = None,


Sort of orthogonal to your changes but why isn't that an actual log level, as in the type?

That's a good question. Should we keep it as a string or refactor to use the logging types? I'm not sure if there's a reason it's this way and not even something like Literal["WARNING", "INFO", ...]

Technically they're numbers, see https://docs.python.org/3/library/logging.html#logging-levels

I would definitely suggest just using logging.INFO etc.

Updated to use int in latest commit

pyrit/cli/frontend_core.py

romanlutz · 2026-02-05T18:48:01Z

pyrit/cli/frontend_core.py

-        self._initializer_names = initializer_names
-        self._env_files = env_files
-        self._log_level = validate_log_level(log_level=log_level)
+        from pyrit.setup import ConfigurationLoader


nit: top of the file

Doesn't seem resolved?

Should be in the latest commit

pyrit/cli/frontend_core.py

romanlutz · 2026-02-05T18:53:00Z

pyrit/cli/frontend_core.py

        Initialize PyRIT context.

+        Configuration is loaded in the following order (later values override earlier):
+        1. Default config file (~/.pyrit/.pyrit_conf) if it exists


Make sure to update devcontainer configuration to get that file into the devcontainer (if it isn't already).

It should be by default, but an explicit check has been added to the devcontainer shell script, as well as explicit creation of .pyrit_conf from .pyrit_conf_example.

.pyrit_conf_example

…to pyrit-config

pyrit/cli/frontend_core.py

rlundeen2 · 2026-02-06T20:05:45Z

.devcontainer/devcontainer_setup.sh


 MYPY_CACHE="/workspace/.mypy_cache"
 VIRTUAL_ENV="/opt/venv"
+PYRIT_CONFIG_DIR="/home/vscode/.pyrit"


Should this be ~/.pyrit?

In the devcontainer that is the home directory.

Makes sense, but I guess wondering if using ~ is more generic for diff containers.

In my experience this tends to fail given that ~ can alias to home for the root user during the build process. But I don't know enough about our Docker build pipeline to confirm it

rlundeen2 · 2026-02-06T20:07:42Z

.devcontainer/devcontainer_setup.sh

+PYRIT_CONFIG_FILE="$PYRIT_CONFIG_DIR/.pyrit_conf"
+
+# Create the .pyrit config directory and copy example config if not exists
+if [ ! -d "$PYRIT_CONFIG_DIR" ]; then


it might be nice to have someone else weigh in on this. I'm hesitant about auto copying things over like this though. @romanlutz who is working on docker things

I'm confused. What I would expect to happen is that my directory at ~/.pyrit shows up at ~/.pyrit inside the container which is /home/vscode/.pyrit.

What is the copying logic meant to copy? The example file? What would that be useful for?

Right now it's also copying over the example if the file doesn't exist which probably isn't useful like you mention.

Would it make sense to copy over ~/.pyrit directory? Including the .env files there?

What would be the most intuitive way to handle discovery and population of the config file in the Docker image? I'm not sure I understand Roman's original request to make sure the file is in the devcontainer, since if the example file is in the git repo then when the Docker image clones and builds it should be included. Is there something I'm missing?

I feel like we have two main options:

Leave .pyrit_conf_example and ask users to create .pyrit_conf using it like we do with our .env file(s)

Deliberately create a .pyrit_conf file with certain values from the example as a template.
I'm in favor of the first given that it's more consistent with how we do environment variables but as I said I think I'm misunderstanding the premise

rlundeen2

My only concerns are I want someone else to look at the docker setup :)

Everything else looks good!

Victor Valbuena added 3 commits January 30, 2026 23:45

tests and base classes

59d4e86

tweaks

6518e39

config-file arg

f012424

ValbuenaVC changed the title ~~Pyrit Config~~ [DRAFT] FEAT PyRIT Config Jan 31, 2026

romanlutz reviewed Feb 5, 2026

View reviewed changes

pyrit/cli/frontend_core.py Outdated Show resolved Hide resolved

romanlutz reviewed Feb 5, 2026

View reviewed changes

pyrit/cli/frontend_core.py Outdated Show resolved Hide resolved

romanlutz reviewed Feb 5, 2026

View reviewed changes

pyrit/cli/frontend_core.py Outdated Show resolved Hide resolved

romanlutz reviewed Feb 5, 2026

View reviewed changes

.pyrit_conf_example Outdated Show resolved Hide resolved

ValbuenaVC changed the title ~~[DRAFT] FEAT PyRIT Config~~ [DRAFT] FEAT: PyRIT Config Feb 5, 2026

ValbuenaVC and others added 3 commits February 5, 2026 11:45

Merge branch 'main' into pyrit-config

785bbc6

precedence

1753576

Merge branch 'pyrit-config' of https://github.com/ValbuenaVC/PyRIT in…

2a3a79d

…to pyrit-config

ValbuenaVC changed the title ~~[DRAFT] FEAT: PyRIT Config~~ FEAT: PyRIT Config Feb 5, 2026

ValbuenaVC marked this pull request as ready for review February 5, 2026 19:54

ValbuenaVC and others added 3 commits February 5, 2026 13:25

Merge branch 'main' into pyrit-config

70df49d

precommit

3d1ff3e

unit tests precommit

930f7ec

rlundeen2 reviewed Feb 5, 2026

View reviewed changes

pyrit/cli/frontend_core.py Outdated Show resolved Hide resolved

rlundeen2 reviewed Feb 5, 2026

View reviewed changes

pyrit/cli/frontend_core.py Outdated Show resolved Hide resolved

fixes

2fdd416

rlundeen2 mentioned this pull request Feb 6, 2026

FEAT Add backend APIs #1354

Open

ValbuenaVC and others added 6 commits February 5, 2026 16:30

Merge branch 'main' into pyrit-config

cf6012d

devcontainer and conf

761e94e

Merge branch 'main' into pyrit-config

9c2b6cc

empty list behavior

3e05974

precommit

dbb2e3f

logging type

3284e19

Merge branch 'main' into pyrit-config

9f775a8

rlundeen2 reviewed Feb 6, 2026

View reviewed changes

rlundeen2 approved these changes Feb 6, 2026

View reviewed changes

Victor Valbuena added 4 commits February 6, 2026 23:23

precommit

5a48b78

precommit mypy

ecc4ab0

logging type

c183e34

logging

0f638bd

Conversation

ValbuenaVC commented Jan 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Tests and Documentation

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ValbuenaVC Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

rlundeen2 Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ValbuenaVC Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ValbuenaVC Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ValbuenaVC Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rlundeen2 left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

ValbuenaVC commented Jan 31, 2026 •

edited

Loading

ValbuenaVC Feb 6, 2026 •

edited

Loading

rlundeen2 Feb 6, 2026 •

edited

Loading

ValbuenaVC Feb 6, 2026 •

edited

Loading

ValbuenaVC Feb 6, 2026 •

edited

Loading

ValbuenaVC Feb 6, 2026 •

edited

Loading