[DOCS] Enumerate ephemeral Data Context use cases#11928
Open
zozo123 wants to merge 2 commits into
Open
Conversation
Adds CI / disposable-compute / no-persistent-filesystem use cases to the Ephemeral Data Context section, per discussion fivetran#11923. Code snippet left DataContext-focused as requested. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for niobium-lead-7998 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Description
Per the discussion in #11923, this adds a short, provider-agnostic enumeration of when an Ephemeral Data Context is a good fit — running in CI, disposable/read-only compute, and quick experimentation — to the Ephemeral section of the Create a Data Context page.
As @joshua-stauffer suggested there, the code snippet is left DataContext-focused (unchanged); this only adds prose listing the additional use cases. No vendor names.
Documentation-only change.
invoke lint— n/a, documentation-only change (no Python touched)