Add moqui-minio enterprise MinIO integration component

[heguangyong]

🧩 Summary

This PR adds a link to a new community component: moqui-minio.

It provides enterprise-grade MinIO object storage integration for the Moqui framework, with production-ready architecture and comprehensive documentation.

---

🚀 Key Features

Core Capabilities

• Bucket Management: Create, update, delete, and list buckets
• Object Operations: Upload, download, delete, list objects (with large file support)
• ElFinder Integration: Web-based file manager with full Chinese UI
• Permission Control: Per-user bucket permissions (READ/WRITE/ADMIN)
• Audit Logging: Full operation history with user/IP tracking

Enterprise Enhancements

• Connection Pooling: Reusable MinIO clients with lifecycle management
• Unified Configuration: Supports environment variables, XML config, and defaults
• Exception Handling: Unified error classification and friendly messages
• Security & Compliance: Sensitive info masking, access validation, and full audit logs
• Monitoring: Connection status, usage statistics, and performance metrics

---

⚙️ Installation

cd runtime/component
git clone https://github.com/heguangyong/moqui-minio.git
cd moqui-minio
../../../gradlew jar

[heguangyong]

@moqui-maintainers
Hi, this PR adds the moqui-minio enterprise integration component.
The "Validate Gradle Wrapper" workflow is waiting for maintainer approval.
Please approve and run the workflow so all checks can complete. Thanks!

[acetousk]

@heguangyong Can we get a PR for minio support that is ONLY for minio with separate PRs for jwt and localization etc?

[heguangyong]

@acetousk Thank you for the valuable feedback! I completely agree with splitting the PR into focused, single-purpose contributions.

Proposed Approach

To make the contribution cleaner and more maintainable, I would like to propose creating a separate repository under the Moqui organization for the moqui-minio component, similar to other Moqui components like:

• moqui/moqui-elasticsearch
• moqui/moqui-hazelcast
• moqui/moqui-camel

Benefits of This Approach

1. Better component isolation - Independent versioning and release management
2. Cleaner contribution workflow - Each feature enhancement can be a separate PR to the component repo
3. Follows Moqui conventions - Consistent with how other integration components are organized
4. Easier maintenance - Component-specific issues and features can be tracked independently

Proposed Steps

Step 1: Create moqui-minio Repository

If this approach is acceptable, could you please:

1. Create a new repository: moqui/moqui-minio
2. Grant me contributor access to push the initial code

Step 2: Initial Core Submission

I will submit the core MinIO functionality ONLY, including:

• MinIO client connection management and pooling
• Basic bucket operations (create, delete, list)
• Object operations (upload, download, delete)
• ElFinder integration for file management
• Core service definitions and entities
• English documentation only

What will NOT be included in the initial submission:

• Localization support (Chinese translations) - will be a separate PR
• Any JWT-related features (if applicable) - will be a separate PR

Step 3: Follow-up PRs

After the core is accepted, I will submit separate PRs for:

1. Localization support - Chinese translations and i18n
2. Any additional enhancements or features

Step 4: Update moqui-framework

I will close this PR (#670) and create a new minimal PR that simply:

• Adds documentation reference to the moqui-minio component
• Includes integration instructions (if needed in the framework itself)

Current Status

I have already:

• ✅ Cleaned up the code and fixed all compilation issues
• ✅ Tested the component successfully with JDK 11 on Windows
• ✅ Verified all features work correctly (bucket management, file operations, ElFinder integration)
• ✅ Prepared the core-only version (without localization)

The component is production-ready and includes:

• Enterprise-grade connection pooling
• Comprehensive error handling
• Complete audit logging
• Permission management
• REST API support

What I Need

To proceed with this plan, I need:

• Confirmation that creating moqui/moqui-minio repository is acceptable
• The repository to be created by a Moqui org admin
• Contributor access to push the initial code

Once the repository is ready, I can have the core functionality PR ready within 1-2 days.

Alternative Approach

If creating a separate repository is not preferred, I can alternatively:

• Keep moqui-minio in my personal GitHub account: https://github.com/heguangyong/moqui-minio
• Submit a minimal PR to moqui-framework that just adds a reference/link to the component
• Manage the component independently with clear documentation for users

Please let me know which approach you prefer, and I'll proceed accordingly.

Thank you for your guidance on making this contribution fit well with the Moqui project structure!

---

发布后的跟进

预期响应 (3-7天)

场景 A: 同意创建仓库 ✅

• 等待 moqui/moqui-minio 仓库创建通知
• 收到 contributor 权限
• 按照 CONTRIBUTING_STRATEGY.md 的阶段3执行

场景 B: 建议其他方案

• 灵活调整,核心原则:只提交 MinIO 核心功能
• 本地化和额外功能单独PR

场景 C: 需要更多信息
准备提供:

• 功能详细列表
• 架构设计图
• 代码示例

如果7天无响应

礼貌地跟进:

Hi @acetousk,

I wanted to follow up on my proposal in PR #670 regarding the moqui-minio component.

I've prepared a clean, core-only version of the component (without localization) and I'm ready to proceed as soon as we decide on the repository approach.

If you have any questions or need additional information, please let me know.

Looking forward to your feedback!

Best regards,
[Your Name]

文件位置

• 完整策略: CONTRIBUTING_STRATEGY.md - 5阶段详细计划
• 验证报告: VERIFICATION_REPORT.md - 组件测试结果
• GitHub PR: Add moqui-minio enterprise MinIO integration component #670
• 你的仓库: https://github.com/heguangyong/moqui-minio