Additional config changes to support AccountDeleter migration #10180
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.
Addresses: https://github.com/NuGet/Engineering/issues/5586 alongside #10165.
This completes the migration for
AccountDeleter
--there was a null ref issue with configs inAccountDeleter
'sJob
's base classesValidationJobBase
(which configures validation storage access) andJsonConfigurationJob
(which configures feature flag storage access). Neither storage accounts are used byAccountDeleter
and recent changes toCloudBlobClientWrapper
had removed a tolerance for nulls in the connection strings. An experimental change toCloudBlobWrapperClient
sought to address this but wasn't successful, but left a BOM removal in code which is an acceptable push. FYI @agr.The
app.config
change is necessary for a break introduced in our deployment pipeline. I will discuss it in the context of an internal PR on this.