Skip to content

feat(plugins): add Sealos#148

Open
yangchuansheng wants to merge 1 commit into
hashgraph-online:mainfrom
yangchuansheng:add-sealos-plugin
Open

feat(plugins): add Sealos#148
yangchuansheng wants to merge 1 commit into
hashgraph-online:mainfrom
yangchuansheng:add-sealos-plugin

Conversation

@yangchuansheng
Copy link
Copy Markdown

Summary

  • Add Sealos to the Development & Workflow community plugins list
  • Mirror the Sealos Codex plugin bundle under plugins/labring/sealos-skills
  • Update plugins.json and the local marketplace entry

Validation

  • python3 scripts/check-alphabetical.py
  • python3 scripts/validate-plugin-pr.py --base-ref origin/main
  • python -m json.tool plugins.json
  • python -m json.tool .agents/plugins/marketplace.json
  • python -m json.tool plugins/labring/sealos-skills/.codex-plugin/plugin.json

Refs labring/sealos-skills#22

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces the 'Sealos Skills' plugin, a comprehensive suite of tools for AI agents to deploy applications to Sealos Cloud. It includes skills for cloud-native readiness assessment, deterministic Docker Compose to Sealos template conversion, and iterative Dockerfile generation, supported by extensive knowledge bases and validation scripts. Feedback was provided on the template converter's fallback logic, which may generate redundant deployment resources when processing Compose files that only contain database services.

Comment on lines +2145 to +2148
if not app_services:
if gateway_services:
app_services = gateway_services[:1]
else:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

If the Docker Compose file contains only database services (e.g., just a postgres service), app_services will be empty. The current logic then picks the first service from service_items as the primary app service. This results in generating both a Kubeblocks Cluster and a standard Deployment for the same database image, which is redundant and likely incorrect for Sealos templates. Consider filtering out services already identified as database services when falling back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant