Declarative bucket and key configuration #450
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#450
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would be great if there was a way to specify all buckets, keys, layouts and other configuration declaratively, i.e. as a configuration file instead of having to use the cli to setup everything after installation. The setup would probably have to be inmutable in this case.
This would make migration to a new machine easier and also guarantee a certain a state of the server to always be present.
From a user's perspective you would define everything once and have the complete
"schema" with all your buckets, keys and so on in a file that you can backup and use to replicate the setup on a new server.
You can try using the Terraform provider at:
relating to:
#678
but im seeking how to configure layout , but i want to make it 100% automate so the problem the ID's i cant know beforehand