Microsite: add example queries to the landing page - #1
Open
jeffreyaven wants to merge 1 commit into
Open
jeffreyaven wants to merge 1 commit into
jeffreyaven wants to merge 1 commit into
Conversation
Add an "Example Queries" section with common queries a practitioner would run to the `entra_id` provider landing page (matching the clickhouse microsite), and regenerate the website landing page. This repository sits on its default branch `stackql-provider` with no long-lived feature branch, so `feature/provider-dev` was created from it for this change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Summary
## Example Queriessection to theentra_idprovider landing page: inventory reads first, then filtered reads, joins and json_extract examples, then provisioning and lifecycle statements. Resource, column and parameter names were checked against the generated provider spec and resource docs.index.md) from the updated header content.This repository sits on its default branch
stackql-providerwith no long-lived feature branch, sofeature/provider-devwas created from it for this change.Verification
website/docs/index.mdis committed from the docs regeneration; a full regeneration also rewrote 440 service pages (the committed service docs are behind the current generator) andprovider-dev/scripts/curate_docs.pystops on a Windows path-length error, both unrelated to this change and left out of this PR.yarn buildof the website succeeds locally.🤖 Generated with Claude Code