Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional configuration files does not work as expected #553

Open
pavlozt opened this issue Oct 20, 2024 · 1 comment
Open

Additional configuration files does not work as expected #553

pavlozt opened this issue Oct 20, 2024 · 1 comment

Comments

@pavlozt
Copy link

pavlozt commented Oct 20, 2024

Simply changing a additional files does not cause a restart mysql and handler notify.
default value for ansible.builtin.template must be force = True :

force: "{{ item.force | default(False) }}"

When the file is not actually different in content, the change will not occur anyway. This is how the ansible template module works.

@pavlozt
Copy link
Author

pavlozt commented Oct 20, 2024

The question is not so straightforward. This is what I read in the documentation:

A list of files that should override the default global my.cnf. Each item in the array requires a "src" parameter which is a path to a file. An optional "force" parameter can force the file to be updated each time ansible runs.

How should this be perceived? In fact, the file will not be ovewritten every time, but only when changes are made on the ansible side.

In this case, you have selected overwrite_global_mycnf: true

I am waiting for your decision as a Creator.

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

No branches or pull requests

1 participant