| Age | Commit message (Collapse) | Author |
|---|
|
|
|
whatever other set of objects.
|
|
|
|
(as seperate objects).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
method). Handle error cases better...
|
|
and format built in config
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
function for bad modules.
|
|
|
|
|
|
if needed.
|
|
needed.
|
|
here as well as other find datasource function.
|
|
|
|
upstart-jobs, boot-hook) as classes as well as some utility methods to fixup
imported modules (ensuring they have the right members/properties) and moving the walking handler callbacks and other part running functionality here.
|
|
which will help unmount.
|
|
|
|
Now there exists a class which processes the user data down to a mime message and just some small utility methods to walk and determine types.
Large amount of content type cleanups & constant creation.
|
|
|
|
|
|
config) as well as file names (for those that have files).
|
|
CloudInit - cut up to only provide some basic init processes
CloudPartData - provided to handlers so that they can fetch needed data without providing the whole enchilda of cloud init.
CloudPaths - holds the paths that should be used, for instances, for non-instances and such.
CloudSemaphores - holds the concept of cloud inits sempaphores, but cleaned up, using context manager to help here.
CloudHandlers - holds the user data handlers to be activated
CloudConfig - the cloud config object (to be cleaned up)
|
|
TODO: maybe just move them to utils?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2. Cleanup main __init__ file with shell additions, constants usage, os.path usage.
|
|
|
