-
Notifications
You must be signed in to change notification settings - Fork 142
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
Unexpected reported change for credentials role in combination with GUI #919
Comments
juliaschindler
added
bug
Something isn't working
new
New issue, this should be removed once reviewed
labels
Oct 1, 2024
if you turn off no_log and turn up verbosity it should show what it sees as a change |
Thanks, I tried using First run:
second run:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Setting up a credential in the AAP GUI and then running the credentials role with the same credential configured in controller_credentials and using "update_secrets: false" reports back "changed" on the first run, "ok" on rerun.
Issue Type
Ansible, Collection, Controller details
Desired Behavior
Setting up a credential in the AAP GUI and then running the credentials role with the same credential configured in controller_credentials and using "update_secrets: false" reports back "ok" on any run.
This is the experienced behaviour with the users role, that has the same "update_secrets" parameter.
Actual Behavior
Setting up a credential in the AAP GUI and then running the credentials role with the same credential configured in controller_credentials and using "update_secrets: false" reports back "changed" on the first run, "ok" on rerun.
First playbook run after setting up the credential already in the AAP GUI:
On further runs:
STEPS TO REPRODUCE
The text was updated successfully, but these errors were encountered: