You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the local_status_page_enabled and remote_status_page_enabled are not idempotent. so it changes always when you run the playbook API change logs:
@petertavenier Again, thank you for reporting this. I researched this over lunch and was able to confirm the bug and have ideas for a fix.
Gory details - When I query a network to compare the proposed (want) and existing (have) settings, it no longer returns the enabled state of the status pages. When I go to compare it basically says "This property isn't set, gotta update!", even thought it may be set properly. It's most likely I'll need to query the settings and merge it into the query data. This fix will have a significant performance impact because it'll require an additional HTTP request for each execution.
It looks like the local_status_page_enabled and remote_status_page_enabled are not idempotent. so it changes always when you run the playbook API change logs:
when using task;
I get the message it is changed;
first I thought is was because of the
"remote_status_page_enabled": null,
but changing the task to:
it also is status "changed";
The text was updated successfully, but these errors were encountered: