Files
storage-minio/.gitea/pull_request_template.md
Rene Nochebuena 1a34b84ee9 feat(storage-minio): initial implementation — MinIO/S3 object storage with lifecycle (v1.0.0)
Introduces code.nochebuena.dev/einherjar/storage-minio — the object storage
starter for the Einherjar framework. Absorbs the minio package from micro-lib,
replacing fmt.Errorf wrapping with core/xerrors.

Interfaces (CT-6: one TypeSpec per file):
- Provider — PutObject, RemoveObject, GetObject, PresignedGetObject, HandleError
- Component — lifecycle.Component + observability.Checkable + Provider + Native()

Implementation:
- New(logger, cfg) Component — client not created until OnInit
- OnInit: minio.New with credentials and transport; bucket existence check
- OnStart: BucketExists PING; logs "minio: connected"
- OnStop: logs "minio: closing client" (minio-go is stateless; no explicit close)
- HealthCheck: BucketExists check; Priority LevelCritical
- Native() *miniogo.Client — escape hatch for operations not in Provider
- HandleError: maps minio-go errors to xerrors (NotFound, AlreadyExists, Internal)

Config (EINHERJAR_MINIO_* env vars):
  Endpoint(required), AccessKey(required), SecretKey(required),
  Bucket(required), UseSSL(false), Region(us-east-1)

- Component interface embeds observability.Identifiable; identifiable.go implements
  ModulePath and ModuleVersion via runtime/debug.ReadBuildInfo() — prints in launcher banner
2026-05-29 16:03:52 +00:00

2.3 KiB

Summary


Type of change

  • Bug fix — non-breaking change that resolves an issue
  • New feature — non-breaking addition of functionality
  • Breaking change — alters existing behavior or public API
  • Documentation update
  • Refactor — no functional change, no new API surface
  • Test improvement

Description


Testing

  • I added or updated tests that cover my changes
  • All tests pass locally — go test ./...
  • No formatting issues — gofmt -l . produces no output
  • No vet warnings — go vet ./... is clean

Checklist

  • At most one exported type per non-test .go file (CT-6)
  • No new external dependencies added without prior discussion in an issue
  • Public API changes are reflected in CHANGELOG.md
  • Breaking changes include a migration note in the PR description above

Contributor License Agreement

This PR will not be merged until the CLA comment is present.

Before a Maintainer reviews your code, you must post the following text as a comment on this PR — not here in the description. PR description checkboxes can be silently toggled by anyone; a comment is a timestamped, author-attributed record that cannot be quietly removed.

Copy and post this exact text as a PR comment:


I have read the Einherjar Contributor License Agreement (CLA.md) and I agree to all its terms. I confirm this Contribution is my original work. I grant the Maintainers the rights described therein, including the right to relicense, and I retain ownership of my copyright. This agreement covers all future Contributions I submit to any Einherjar repository under this account.


First time contributing? Read CLA.md for the full agreement before posting the comment.

If you are contributing on behalf of a company, an authorized representative of that company must post the comment.