Add custom WireServer POST responses #250
Merged
Conversation
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
peytonr18
approved these changes
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes
This PR allows the use of custom response code sequences for the mocked WireServer. Using a new CLI flag, the user can specify which file they would like the WireServer to respond with. This also introduced the per-response delay for the wireserver. Both of these features are already implemented for IMDS.
Along with this improvement, I also ran a formatter on save to ensure that everything stayed consistent. This makes the PR look bigger than it actually is.
How to use
This PR runs automatically in the E2E Testing pipeline and should not be run locally. Reviewers should examine the Provisioning Agent container logs, Testing Server container logs, KVP logs, and Azure-Init logs which are found at the bottom of the pipeline.
Testing done
This PR does not modify any of the Azure-init code, so testing has been done through the CI pipeline that is associated with it.
Work Items
This PR resolves #246 and completes the last child of #242.