Declare what MinIO buckets, IAM policies, ILM policies you want, and let MinIO Manager do the work.
- GitHub repository: https://github.com/alveel/minio-manager/
- Documentation https://alveel.github.io/minio-manager/
The concept for management is to have so-called "bucket groups".
Each bucket group is managed by an account that only has access to buckets in that group.
It should be noted that this is explicitly intended for the creation and updating of resources in MinIO. It does not delete any resources anywhere.
Install the environment and the pre-commit hooks with
make installYou are now ready to start development on your project! The CI/CD pipeline will be triggered when you open a pull request, merge to main, or when you create a new release.
To quickly configure a local development MinIO, you can run
make run-test-environmentNote: requires Podman!
Copy .env.example to config.env and modify to your liking.
By default, MinIO Manager automatically loads a .env file from config.env. Of course, you can configure your IDE to load .env or any other env file instead.
Now you can use debug tools in your IDE to run the Python code.
Configure your debugger to run the Python module minio_manager with the environment variables from .env.
A sample debugger configuration for Visual Studio Code is configured in .vscode/launch.json and should be directly available from "Run and Debug".
Find local MinIO installation on http://localhost:9000.
When you are finished, run
make stop-test-environmentNote that the created secrets-insecure.yaml will not be removed automatically and will get overwritten by the setup command.
To finalize the set-up for publishing to PyPi or Artifactory, see here. For activating the automatic documentation with MkDocs, see here. To enable the code coverage reports, see here.
Check the open enhancement issues.
Repository initiated with fpgmaas/cookiecutter-pdm.