fix: Standardize HttpConfiguration use within examples #188
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
spanglerco
commented
Jan 8, 2026
rbell517
approved these changes
Jan 8, 2026
cameronwaterman
approved these changes
Jan 8, 2026
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.
What does this Pull Request accomplish?
Standardize all examples to the same format for specifying
HttpConfiguration. Specifically, they all default to using the auto-configuration (requires running on a managed system or within a notebook on the server) with comments explaining how to point to a specific instance. The commented out configuration doesn't not specify an API key, but has a place to put one.I also corrected a few imports that were referencing private modules instead of the public ones.
Mostly implemented by Copilot based on manual edits to the testmonitor results example.
Why should this Pull Request be merged?
Consistency makes it easier to use our examples. This format also avoids Snyk flagging each example and requiring an explicit ignore every time we add an example.
What testing has been done?
Copied the DFS
query_read_dataexample into a Juypter notebook and verified it ran without modification. Edited the example to use a URI and API key and was able to run it locally as well.