Closed MatthiasKunnen closed 2 months ago
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @AugustusKling click here for bot help
Regarding implementation, to avoid breaking changes, I would add a names parameter and keep the existing one. Is the best practice for Ansible?
You can also change the type of the current name
parameter to list
(elements: str
). Since locale names cannot contain commas this will be backwards compatible: Ansible converts strings to lists by splitting by comma.
(If locale names could contain commas this would not be OK, in that case adding a new list option names
and making name
and names
mutually exclusive would be best.)
Summary
The locale_gen module currently allows for a single locale to be configured at a time. Using a
loop
here isn't the most efficient because both the detection of the current state and the generation of the locale after change needs to be run for every locale. If there are no objections, I would like to add the ability to configure multiple at the same time.Regarding implementation, to avoid breaking changes, I would add a names parameter and keep the existing one. Is the best practice for Ansible?
Issue Type
Feature Idea
Component Name
locale_gen
Additional Information
Code of Conduct