FEAT: Standardizing AIRTInitializer#1578
Open
ValbuenaVC wants to merge 7 commits intomicrosoft:mainfrom
Open
Conversation
romanlutz
reviewed
Apr 8, 2026
added 2 commits
April 8, 2026 23:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
A very small PR to standardize the AIRT initialization flow.
AZURE_SQL_DB_CONNECTION_STRINGandAZURE_STORAGE_ACCOUNT_DB_DATA_CONTAINER_URL.GLOBAL_MEMORY_LABELSis used to store username and current operation name. For backwards compatibility, these areoperatorandoperationin.pyrit_conf, andusernameandop_namein the memory labels respectively.GLOBAL_MEMORY_LABELS. Users seeking to change the operation name can do so by changing the value in.pyrit_confand re-running the initializer.operationandoperatorin the config to prevent regression.Tests and Documentation
tests.unit.setup.test_airt_initializer.