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
The prepared query is created during the first run, but not updated with the new attributes in the second run.
What behaviour did you expect instead
Changing attributes should be reflected in Consul.
Output log
Output of the second run:
Info: Applying configuration version '1718372736'
Debug: Prefetching default resources for consul_prepared_query
Debug: prefetching for consul
Debug: found {:name=>"consul", :id=>"a319fb62-d604-1a4d-e4b8-f54c6fbe448c", :token=>"", :service_failover_dcs=>["dc1", "dc2"], :ttl=>"10s", :service_only_passing=>false, :ensure=>:present}
Debug: Finishing transaction 12260
Debug: Storing state
Debug: Pruned old state cache entries in 0.00 seconds
Debug: Stored state in 0.00 seconds
Notice: Applied catalog in 0.02 seconds
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered:
gmenuel
changed the title
consul_prepared_query does'nt support updating
consul_prepared_query doesn't support updating
Jun 14, 2024
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
When running :
And then in another run, we change the service_failover_dcs (for exemple, I've seen the same behavior with other attributes) :
What are you seeing
The prepared query is created during the first run, but not updated with the new attributes in the second run.
What behaviour did you expect instead
Changing attributes should be reflected in Consul.
Output log
Output of the second run:
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: