Commit graph

12 commits

Author SHA1 Message Date
Patrick Uiterwijk
f3d2bde922 Give staging fedmsg also prod policy since we have prod->stg message flow
Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
2018-04-17 02:24:14 +02:00
Ralph Bean
e9cbb411ec Try adding greenwave and waiverdb to the stg fedmsg routing policy. 2017-10-19 15:19:46 +00:00
Ralph Bean
e15e880221 Consider the qa network too when building the stg fedmsg routing policy. 2016-03-23 19:14:43 +00:00
Ralph Bean
ceb8e0b73d List only stg hosts in the stg policy and prod hosts in the prod policy. 2015-06-12 17:03:00 +00:00
Ralph Bean
c2fc9578c8 Sort things for idempotence. 2015-06-12 16:51:36 +00:00
Ralph Bean
d9b491c892 We don't have access to facts like ansible_fqdn at this point. 2015-06-12 16:47:53 +00:00
Ralph Bean
c41f3c4b59 Iterate over hosts, not vars. 2015-06-12 16:45:41 +00:00
Ralph Bean
11bde05e66 Debug statement. 2015-06-12 16:44:14 +00:00
Ralph Bean
271300e94c Try passing in the list of hosts a different way. 2015-06-12 16:42:46 +00:00
Ralph Bean
a91f4964fc Declare filter. 2015-06-12 16:30:46 +00:00
Ralph Bean
99c75f405b This will always be there. 2015-06-12 16:29:45 +00:00
Ralph Bean
60dbdd00cf Try dynamically generating some fedmsg config from group/host vars in staging. 2015-06-12 16:27:45 +00:00