add openmetadata recipe

[PubChimps]

Summary

Adding an openmetadata example to the recipe catalog!

Type of Change

• Feature
• Bug fix
• Refactor / Code quality
• Performance improvement
• Documentation
• Tests
• Security fix
• Build / Release
• Other (specify below)

Testing

This has been tested, please let me know if I can help setting up an openmetadata env to test or share a recording of my test

Related Issues

Relates to #ISSUE_ID
Discussion: LINK (if any)

Screenshots/Demos (for UX changes)

Before:

After:

Email:
[email protected]

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

❌ Status: BLOCKED - One or more recipes have MEDIUM risk or higher

⚠️ Merge Protection: This PR cannot be merged until security concerns are addressed.
Repository maintainers can override this decision if needed.

📊 Scan Summary:

• Total recipes scanned: 1
• Blocked recipes: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (MEDIUM risk)

🔗 View detailed scan results in the workflow artifacts.

[PubChimps]

Would love some clarification on extensions in recipes... if I already have an openmetadata extension set up in goose this recipe works, I thought the recipe would create an extension if there wasn't one, but it does not, this is expected, right?

[iandouglas]

is the verbose flag required?

[iandouglas]

if I already have an openmetadata extension set up in goose this recipe works, I thought the recipe would create an extension if there wasn't one, but it does not, this is expected, right?

I believe if you have an extension that matches the name/title then goose will use the one you already have; defining the whole structure of the extension within the recipe is more for first-time extension installations.

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.