Bug #4030
Kamaki should raise errors for incompatible cloud names in config file
| Status: | Closed | Start date: | 06/17/2013 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | 06/17/2013 | |
| Assignee: | Stavros Sachtouris | % Done: | 100% |
|
| Category: | kamaki | Spent time: | 1.00 hour | |
| Target version: | v0.9 | Estimated time: | 1.00 hour |
Description
Implement a new class of Exceptions: KamakiConfigError
Implement a KamakiConfigCloudNameError as extentions of KamakiConfigError
Modify regex to acceptas cloud names: ([$#-:@\w]+)
Any cloud name not matching this regex will cause a KamakiConfigCloudNameError
Associated revisions
Make cloud prefix a global settings
Refs: #4030
Create InvalidCloudNameError, raise it when needed
Refs: #4030
Make cloud prefix a global settings
Refs: #4030
Create InvalidCloudNameError, raise it when needed
Refs: #4030
Fix write recovery bug in kamaki.cli.config
write failed to recover config memory repr. after writing in disk
Refs: #4030
Fix write recovery bug in kamaki.cli.config
write failed to recover config memory repr. after writing in disk
Refs: #4030
History
#1 Updated by Stavros Sachtouris almost 10 years ago
- % Done changed from 0 to 100
#2 Updated by Stavros Sachtouris almost 10 years ago
The error is CloudNameError and extents the ConfigParser.Error
#3 Updated by Stavros Sachtouris almost 10 years ago
- Status changed from New to Closed