| Age | Commit message (Collapse) | Author |
|---|
|
|
|
should already be modified
|
|
|
|
|
|
|
|
with non-real read/write paths is easier.
|
|
|
|
|
|
a. This allows for more properties to be added as needed in the future, instead of being very restrictive.
2. Fix up all uses of the url reading to now use this new response object.
3. Also fixup user data including, such that if no response actual occurs the url content is not further processed.
|
|
2. Adjust that name in the cloud.cfg
3. Add in the ability to specify a dictionary that is the transform instead of a list
which makes the config look nicer when users have custom transforms with arguments and such.
|
|
|
|
since its not currently being called that way
|
|
1. Just let them have no prefix (ie blank) unless this isn't wanted later.
|
|
desired.
|
|
2. Check lowercase name against .py instead of unknown case.
|
|
2. Adjust so file contents will join with a string instead of appending to something that might not be a string
|
|
|
|
1. Add a comment onto why this is done
2. Fix the usage of range to search the list and not a string
3. Make the filecontents template just one multiline variable.
|
|
|
|
|
|
|
|
|
|
Some of the cleanups were the following
1. Using standard (logged) utility functions for sub process work, writing, reading files, and other file system/operating system options
2. Having distrobutions impelement there own subclasses to handle system specifics (if applicable)
3. Having a cloud wrapper that provides just the functionality we want to expose (cloud.py)
4. Using a path class instead of globals for all cloud init paths (it is configured via config)
5. Removal of as much shared global state as possible (there should be none, minus a set of constants)
6. Other various cleanups that remove transforms/handlers/modules from reading/writing/chmoding there own files.
a. They should be using util functions to take advantage of the logging that is now enabled in those util functions (very useful for debugging)
7. Urls being read and checked from a single module that serves this and only this purpose (+1 for code organization)
8. Updates to log whenever a transform decides not to run
9. Ensure whenever a exception is thrown (and possibly captured) that the util.logexc function is called
a. For debugging, tracing this is important to not just drop them on the floor.
10. Code shuffling into utils.py where it makes sense (and where it could serve a benefit for other code now or in the future)
|
|
to users.
It is similar to the final msg one, but is used at the start of cloud init instead.
|
|
|
