(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2021-12-03T20:11:46+00:00 2021-12-03T20:11:46+00:00 Brett Holman bholman.devel@gmail.com 2021-12-03T20:11:46+00:00 urn:sha1:039c40f9b3d88ee8158604bb18ca4bf2fb5d5e51 This attempts to standardize unit test file location under test/unittests/ such that any source file located at cloudinit/path/to/file.py may have a corresponding unit test file at test/unittests/path/to/test_file.py. Noteworthy Comments: ==================== Four different duplicate test files existed: test_{gpg,util,cc_mounts,cc_resolv_conf}.py Each of these duplicate file pairs has been merged together. This is a break in git history for these files. The test suite appears to have a dependency on test order. Changing test order causes some tests to fail. This should be rectified, but for now some tests have been modified in tests/unittests/config/test_set_passwords.py. A helper class name starts with "Test" which causes pytest to try executing it as a test case, which then throws warnings "due to Class having __init__()". Silence by changing the name of the class. # helpers.py is imported in many test files, import paths change cloudinit/tests/helpers.py -> tests/unittests/helpers.py # Move directories: cloudinit/distros/tests -> tests/unittests/distros cloudinit/cmd/devel/tests -> tests/unittests/cmd/devel cloudinit/cmd/tests -> tests/unittests/cmd/ cloudinit/sources/helpers/tests -> tests/unittests/sources/helpers cloudinit/sources/tests -> tests/unittests/sources cloudinit/net/tests -> tests/unittests/net cloudinit/config/tests -> tests/unittests/config cloudinit/analyze/tests/ -> tests/unittests/analyze/ # Standardize tests already in tests/unittests/ test_datasource -> sources test_distros -> distros test_vmware -> sources/vmware test_handler -> config # this contains cloudconfig module tests test_runs -> runs 2021-10-16T00:53:42+00:00 James Falcon james.falcon@canonical.com 2021-10-16T00:53:42+00:00 urn:sha1:a9501251aadf6d30192f7bd7debeabc9c3e29420 Also added supporting distro/datasource classes and updated tests that have a `get_cloud` call. 2021-09-01T14:50:37+00:00 Andrew Bogott Andrewbogott@gmail.com 2021-09-01T14:50:37+00:00 urn:sha1:db72c841c2ec0d94d366df7fa623e82e91e2201c The current code starts the puppet agent and also sets autostart in all cases. This conflicts with a common pattern where puppet itself manages the agent and autostart state. For example, in my deploy puppet disables the puppet agent and replaces it with a cron. This causes various races both within this cloud-init unit and within puppet itself while cloud-init and puppet fight over whether or not to enable the service. 2021-08-13T01:06:28+00:00 James Falcon therealfalcon@gmail.com 2021-08-13T01:06:28+00:00 urn:sha1:1c3b10b58768ec4c70384f4a7af7ce956518fe7c * Replace broken httpretty tests with mock Certain versions of python/httpretty don't work correctly using https URIs. #960 recently added httpretty tests using https. This commit replaces the httpretty tests that were failing on https with mocks of readurl instead. 2021-08-10T15:14:23+00:00 Gabriel Nagy gabrielnagy@me.com 2021-08-10T15:14:23+00:00 urn:sha1:9893dfcd2f0be92197d707236cbd44cb7452364d - update the puppet module to support AIO installations by setting `install_type` to `aio` - make the install collection configurable through the `collection` parameter; by default the rolling `puppet` collection will be used, which installs the latest version) - when `install_type` is `aio`, puppetlabs repos will be purged after installation; set `cleanup` to `False` to prevent this - AIO installations are performed by downloading and executing a shell script; the URL for this script can be overridden using the `aio_install_url` parameter - make it possible to run puppet agent after installation/configuration via the `exec` key - by default, puppet agent will run with the `--test` argument; this can be overridden via the `exec_args` key 2020-06-08T16:49:12+00:00 Scott Moser smoser@brickies.net 2020-06-08T16:49:12+00:00 urn:sha1:3c551f6ebc12f7729a2755c89b19b9000e27cc88 This was painful, but it finishes a TODO from cloudinit/subp.py. It moves the following from util to subp: ProcessExecutionError subp which target_path I moved subp_blob_in_tempfile into cc_chef, which is its only caller. That saved us from having to deal with it using write_file and temp_utils from subp (which does not import any cloudinit things now). It is arguable that 'target_path' could be moved to a 'path_utils' or something, but in order to use it from subp and also from utils, we had to get it out of utils. 2020-06-02T16:06:07+00:00 Joshua Powers josh.powers@canonical.com 2020-06-02T16:06:07+00:00 urn:sha1:d53921ea3396c8301c65cad3abf04b4542d4b7a0 This fixes issues with closing brackets not matching the opening bracket's line and continuation line under-idented for hanging indent. 2020-03-19T16:01:15+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-03-19T16:01:15+00:00 urn:sha1:ade47866aa2f81ab0f3baabbb1fc1e484abdb741 These classes don't use `self.logs` anywhere in their body, so we can remove the `with_logs = True` setting from them. These instances were found using astpath[0], with the following invocation: astpath "//Name[@id='with_logs' and not(ancestor::ClassDef//Attribute[@attr='logs'])]" [0] https://github.com/hchasestevens/astpath 2019-10-31T15:01:10+00:00 Matthias Baur m.baur@syseleven.de 2019-10-31T15:01:10+00:00 urn:sha1:d3e71b5e843edf73eb7da511a032d987e314bd69 This change adds two new parameters: * csr_attributes * csr_attributes_path Those parameters allow to configure the content of the csr_attributes.yaml file. See https://puppet.com/docs/puppet/latest/config_file_csr_attributes.html 2017-09-05T17:03:59+00:00 Lars Kellogg-Stedman lars@redhat.com 2017-09-05T17:03:59+00:00 urn:sha1:a3649e03206a3596131413956ea7ecc18790ec73 This moves the base test case classes into into cloudinit/tests and updates all the corresponding imports.