-
Notifications
You must be signed in to change notification settings - Fork 2.3k
add openmetadata recipe #5076
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
add openmetadata recipe #5076
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
47 changes: 47 additions & 0 deletions
47
documentation/src/pages/recipes/data/recipes/use-openmetadata.yaml
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| version: 1.0.0 | ||
| title: Use OpenMetadata | ||
| description: Interact with OpenMetadata in Goose via OpenMetadata MCP Server to generate SQL or propagate classifications | ||
| instructions: Utilize OpenMetadata tools to search for, retrieve, and modify metadata related to data assets such as tables, dashboards, and glossaries. Adhere to specified output formats like JSON for search queries and maintain structured responses using Markdown for human-readable information. | ||
| extensions: | ||
| - type: stdio | ||
| name: openmetadata | ||
| cmd: npx | ||
| args: | ||
| - -y | ||
| - mcp-remote | ||
| - http://localhost:8585/mcp | ||
| - --auth-server-url=http://localhost:8585/mcp | ||
| - --client-id=openmetadata | ||
| - --clean | ||
| - --header | ||
| - Authorization:${AUTH_HEADER} | ||
| envs: {} | ||
| env_keys: | ||
| - AUTH_HEADER | ||
| timeout: 300 | ||
| description: '' | ||
| bundled: false | ||
| settings: | ||
iandouglas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| temperature: 0.0 | ||
| activities: | ||
| - Generate SQL Given FQN | ||
| - List Tables Given FQN | ||
| - Propagate changes in certification/owner/tags to tables given FQN | ||
| parameters: | ||
| - key: fqn | ||
| input_type: string | ||
| requirement: required | ||
| description: The fully qualified name of the asset in openmetadata you'd like an agent to act on | ||
| prompt: | | ||
| Take classifications from {{ fqn }} and apply them to all the tables that are listed in {{ fqn }} | ||
|
|
||
| Here's what to do step by step: | ||
|
|
||
| 1. **Verify {{ fqn }} exists in openmetadata** | ||
| 2. **Ask user if they will be propagating the {{ fqn }} owner/certification or a particular tag** | ||
| 3. **Get details of {{ fqn }} in openmetadata** | ||
| - the owner/certification/tag to be applied to other assets | ||
| 4. **List tables of {{ fqn }}** | ||
| 5. **Patch all tables that are returned** | ||
| author: | ||
| contact: nickacosta | ||
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.