45fe10bac1
- Fixed get_persistent_device_from_unix_node The method get_persistent_device_from_unix_node takes a device path and looks up it's basename to be present as persistent variant below the given schema, e.g by-id. However if the method receives an already persistent device path e.g from /dev/mapper the persistent schema representation will only match a numbered dm-N device and not the map name. The method then returns nothing but should return the original device path. This caused bad after effects like reported in Issue SUSE-Enceladus/azure-li-services#163 - [doc] Add user documentation about the usage of the embedded Vagrantfile - Document the usage of the `vagrantconfig.embedded_vagrantfile` attribute - Remove the suggestion to generate the ssh keys during image creation (this results in **all** boxes having the same ssh host keys, which is pretty dangerous if someone would use a vagrant box in a production environment.) - Stop recommending veewee, this project is dead - Replace forgotten hard coded number with {schema_version} - Fix test breakage when /etc/kiwi.yml is present The unit test for the RuntimeConfig class are also testing the default values in some functions. To work around a possibly existing ~/.config/kiwi/config.yml, several functions change the value of HOME. This is unfortunately not sufficient if a /etc/kiwi.yml exists, as that one is taken as a fallback *if* ~/.config/kiwi/config.yml isn't present. This issue is fixed by creating a default_runtime_config with os.path.exists patched to return False. Thereby none of the runtime configuration files will be taken into account. OBS-URL: https://build.opensuse.org/package/show/Virtualization:Appliances:Builder/python-kiwi?expand=0&rev=143 |
||
|---|---|---|
| .gitattributes | ||
| .gitignore | ||
| python-kiwi-rpmlintrc | ||
| python-kiwi.changes | ||
| python-kiwi.spec | ||
| python-kiwi.tar.gz | ||