The keyword default applies to any architecture not explicitly listed. Each config is a dictionary which must have an entry for arches, specifying which architectures that config entry is for. Both the primary and security keys take a list of configs, allowing mirrors to be specified on a per-architecture basis. Primary: (array of object) The primary and security archive mirrors can be specified using the primary and security keys, respectively. When a suite is disabled using disable_suites, its entry in sources.list is not deleted it is just commented out.

Handled on a per-distro basis, so consult documentation forĬloud-init’s distro support for instructions on using There are configuration options such asĪpt_get_wrapper and apt_get_command that control howĬloud-init invokes apt-get. This module handles both configuration of apt options and adding apk_repos : alpine_repo : base_url : ' community_enabled : true testing_enabled : true version : 'edge' local_repo_base_url : ' Apt Configure # apk_repos : alpine_repo : community_enabled : true version : 'v3.12' # - Example3 - # Create repositories file for Alpine Edge main, community, and # testing using a specified mirror site and also a local repo. apk_repos : preserve_repositories : true # - Example2 - # Create repositories file for Alpine v3.12 main and community # using default mirror site. # Keep the existing /etc/apk/repositories file unaltered. Then uses ansible-pull to run the playbookĪctivate only on keys: ansible Config schema: This module installs ansible during boot and This module provides ansible integration forĪugmenting cloud-init’s configuration of the local

A 5 year timeline may also be expected for changed keys. Key’s expected value changes, the key will be marked changed with aĭate. Use ofĭeprecated keys may cause warnings in the logs. Scheduled to be removed in 27.1 (first release in 2027). For example, a key that isĭeprecated in version 22.1 (which is the first release in 2022) is Keys that have been marked as deprecated or changed may be removed orĬhanged 5 years from the date of deprecation. This allows cloud-init to evolve as requirements change, and to adoptīetter practices without maintaining design decisions indefinitely.

Keys may be documented as deprecated, new, or changed. Toggle table of contents sidebar Module reference # Deprecation schedule and versions #

Changing unity cloud build repo