Skip to content

Conversation

@AlexandarY
Copy link

While not the most popular option a lot of people use it to get LXD up and running fast. Changes made:

  • Added variable to control how lxd is expected to be installed. Defaults to deb. If support for non-Debian family OS's is expected to be handled by the module, it might make sense to rename the deb option to something else. As per the project description, it doesn't seem to be any such plans.
  • Added logic to determine how to install the package (package resource or snap exec). Atm it is expected that snapd will be managed by the module, but I can easily switch it to be a configurable option that defaults to true.
  • Included tests for this logic

AlexandarYovchev and others added 9 commits January 7, 2022 14:47
While not the most popular option a lot of people use it to get LXD
up and running fast. Changes made:

* Added variable to control how `lxd` is expected to be installed. Defaults to `deb`.
* Added logic to determine how to install the package (package resource or snap exec)
Previously, when running `class { 'lxd': ensure => absent}` it would
uninstall lxd and then attempt to change config values, which would result
in errors. As such it's better in such case to do that before removing lxd.
* Included tests for all supported OS's as per metadata.json
* Add test to validate install & uninstall order
* Fix tests for deb & snap installs
The change would make it easier for future support of non-Debian family OS's.
@AlexandarY
Copy link
Author

Closing this one as I messed up branches & included untested commits.
The PR was re-opened via #3

@AlexandarY AlexandarY closed this Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants