Skip to content
This repository has been archived by the owner on Jan 17, 2022. It is now read-only.

Option to choose status bucket #1

Open
Joacchim opened this issue Feb 7, 2011 · 0 comments
Open

Option to choose status bucket #1

Joacchim opened this issue Feb 7, 2011 · 0 comments
Labels
enhancement

Comments

@Joacchim
Copy link
Contributor

Joacchim commented Feb 7, 2011

An option allowing to give the name of the status bucket to be used would prevent problems caused by the bucket names limitations (255 chars, ...).
Joacchim added a commit that referenced this issue Feb 25, 2015
@Joacchim
Switch config file format to JSON + Add status backend option
4ae56fe 
 - The config file format is now JSON instead of ini
 - The use can now specify a configuration for the status backend/bucket
 (Still unused in the backend)

Addresses and goes further than issue #1
WIP for issue #24
Joacchim added a commit that referenced this issue Feb 25, 2015
@Joacchim
Add default POSIX backend for status storage
e93097b 
 - Either through CLI options or Config File, default is now enforced
 - The behavior is to use the directory ~/.cloudmig as the status storage.

Related to issue #1
Joacchim added a commit that referenced this issue Mar 16, 2015
@Joacchim
Adding options to enable S3 backend usage
375e38c 
- Provide status bucket name through an option (allows use of existing buckets
for status storage)
- Provide the location constraint (Fixes status store creation when using S3
backend)

Addresses issue #1
Joacchim added a commit that referenced this issue Apr 10, 2015
@Joacchim
Switch config file format to JSON + Add status backend option
902cc7c 
 - The config file format is now JSON instead of ini
 - The use can now specify a configuration for the status backend/bucket
 (Still unused in the backend)

Addresses and goes further than issue #1
WIP for issue #24
Joacchim added a commit that referenced this issue Apr 10, 2015
@Joacchim
Add default POSIX backend for status storage
aca57a6 
 - Either through CLI options or Config File, default is now enforced
 - The behavior is to use the directory ~/.cloudmig as the status storage.

Related to issue #1
Joacchim added a commit that referenced this issue Apr 10, 2015
@Joacchim
Adding options to enable S3 backend usage
3d54a4f 
- Provide status bucket name through an option (allows use of existing buckets
for status storage)
- Provide the location constraint (Fixes status store creation when using S3
backend)

Addresses issue #1
@nicolasb827 nicolasb827 mentioned this issue Aug 28, 2018
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Joacchim