Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-06-04

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:00 brousch joined #salt
00:04 pbandark1 joined #salt
00:10 VR-Jack-H joined #salt
00:32 Tantagel joined #salt
00:40 jeddi joined #salt
00:50 iggy absolute-: also check the note about cmd.wait being deprecated
00:58 Shirkdog joined #salt
01:00 edrocks joined #salt
01:19 wavded joined #salt
01:27 edrocks_ joined #salt
01:48 ilbot3 joined #salt
01:48 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.6, 2016.11.5 <+> Support: https://www.saltstack.com/support/ <+> 1st Salt Cloud Working Group meeting June 1st, 2017 https://goo.gl/o2OK49 <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic <+> We are volunteers and may not have immediate answers
02:46 sh123124213 joined #salt
02:55 fritz09 joined #salt
03:12 zerocoolback joined #salt
03:15 mpanetta joined #salt
03:18 armyriad joined #salt
03:29 edrocks_ joined #salt
03:35 mikea joined #salt
03:42 justan0theruser joined #salt
03:44 sh123124213 joined #salt
03:49 armguy joined #salt
04:22 sjorge joined #salt
04:29 zulutango joined #salt
04:41 Antiarc joined #salt
04:49 Antiarc joined #salt
05:07 mosen joined #salt
05:31 edrocks joined #salt
05:44 nafg joined #salt
05:44 nafg__ joined #salt
05:45 sh123124213 joined #salt
05:46 _KaszpiR_ joined #salt
05:47 ahrs joined #salt
05:51 evle1 joined #salt
06:10 armyriad joined #salt
06:36 vodik joined #salt
06:36 candyman89 joined #salt
06:44 Inveracity joined #salt
06:56 sh123124213 joined #salt
07:06 Trauma joined #salt
07:45 ZanZino joined #salt
07:46 ZanZoni joined #salt
07:55 ProT-0-TypE joined #salt
08:01 Bock joined #salt
08:04 Bock joined #salt
08:07 preludedrew joined #salt
08:11 oida_ joined #salt
08:16 impi joined #salt
08:24 mugsie joined #salt
08:24 mugsie joined #salt
08:41 bluenemo joined #salt
09:01 Trauma joined #salt
09:18 impi joined #salt
09:21 fracklen joined #salt
09:33 garethhowell left #salt
09:40 mikecmpbll joined #salt
09:45 jeddi joined #salt
09:51 pbandark joined #salt
10:33 candyman88 joined #salt
10:34 inad922 joined #salt
10:44 ronnix joined #salt
10:46 SaltyVagrant joined #salt
10:48 mystik joined #salt
10:54 bast joined #salt
10:54 bast joined #salt
11:00 daxroc Can you remove a minions key within a state or orchestration ?
11:02 Neighbour yes, look at the 'wheel' execution module
11:22 daxroc Neighbour: thanks
11:22 daxroc What would be the best way to get a list of minion ids matching a grain  - realistic it should only be one
11:22 daxroc from within the orchestration/state ?
11:23 daxroc * the data provided from the triggered event is present only in a grain and not exported to the mine
11:36 edrocks joined #salt
11:49 daxroc So I guess my ask is,  From an orchestration how do I get a list of minion ids only knowing a grain that's on them. Can I use runner here ? as you would for mine eg. saltutil.runner name='mine.get' tgt='G@ec2:instance_id:i.....'   fun=?
11:50 daxroc *I'm wanting to delete the minion key for the returned match ( should only be one )
11:56 zerocoo__ joined #salt
12:15 mavhq joined #salt
12:37 mikecmpbll joined #salt
12:57 sh123124213 joined #salt
12:57 Hydrosine joined #salt
13:03 Inverakitty joined #salt
13:06 LordOfLA joined #salt
13:08 daxroc Need some guidance here, is using the mine the best way to find a minions id based on a grain set on that minion.  My use case is I've an event pushing the value of that grain into the event bus *external and a reactor  to do something on that event. So what would be the best way to target that minion using the grain value - it should be unique.
13:37 Rubin joined #salt
13:56 nethershaw joined #salt
14:26 Tantagel joined #salt
14:41 XenophonF joined #salt
14:42 fxhp joined #salt
15:04 sknebel_2 joined #salt
15:06 sh123124213 joined #salt
15:12 cyborg-one joined #salt
15:38 sh123124213 joined #salt
16:19 rwaweber joined #salt
16:22 rwaweber joined #salt
16:23 rwaweber joined #salt
16:28 fracklen joined #salt
16:29 rwaweber joined #salt
16:29 rwaweber joined #salt
16:29 rwaweber left #salt
16:34 dxiri joined #salt
16:40 edrocks joined #salt
16:45 candyman88 joined #salt
16:47 dxiri joined #salt
16:49 candyman88 joined #salt
16:56 lorengordon is there a state output option that only lists failed states? i'm poring over the docs and the cli help, and have tried a dozen or so variations, but i can't seem to find a way to only output failed states
16:56 lorengordon i feel like i must be missing something obvious
16:59 XenophonF you could always output in json and then use a parser to filter the results
16:59 XenophonF but there's probably a way to configure the outputter - just a sec, let me check
17:00 Tantagel try 'grep'
17:01 XenophonF well, grep kind of fails on structured data
17:01 XenophonF i'd go the json parser route tbh
17:02 Tantagel either way not a Salt question really
17:02 Tantagel there are some output formatters you can use
17:02 Tantagel https://docs.saltstack.com/en/2015.8/ref/output/all/index.html
17:03 Tantagel yaml or json + another tool extract is the best idea
17:06 sh123124213 joined #salt
17:14 dxiri joined #salt
17:23 XenophonF sorry lorengordon wish i had a better answer for you
17:24 XenophonF you could try using one of the returners
17:24 XenophonF then you could use database queries
17:25 XenophonF e.g., https://docs.saltstack.com/en/latest/ref/returners/all/salt.returners.sqlite3_return.html
17:46 SaltyVagrant joined #salt
17:55 shred joined #salt
17:59 candyman88 joined #salt
18:00 sh123124213 joined #salt
18:03 dxiri joined #salt
18:14 lorengordon yeah, thanks, parsing the json return is easy enough, just seems surprising that among all the state output options none of them seem to filter on the state result
18:16 lorengordon grep is a pretty terrible approach to parsing a state return. way too much variation. i'd probably use jq if i wanted another cli utility
18:22 Rumbles joined #salt
18:22 dxiri joined #salt
18:23 dxiri joined #salt
18:26 cyborg-one joined #salt
18:37 dxiri joined #salt
18:42 edrocks joined #salt
18:51 sh123124213 joined #salt
18:55 dxiri joined #salt
19:00 arif-ali joined #salt
19:08 fracklen joined #salt
19:09 shred joined #salt
19:14 dxiri joined #salt
19:24 Yamazaki-kun joined #salt
19:39 dxiri joined #salt
19:44 monokrome joined #salt
19:53 absolute- Guys, if I have a state file
19:53 absolute- and, reading top to bottom, I have state1, state2, state3
19:53 absolute- State 2 and 3 have a dependency on state1 (say `require`) - What order do state2 and state3 get executed in?
19:56 mr_kyd joined #salt
20:01 amcorreia joined #salt
20:25 rewbycraft absolute-: States get executed in the order they are defined, unless a "require" (or "watch", etc) statement overrides it. So in your example: state1 state2 state3 (see: https://docs.saltstack.com/en/latest/ref/states/ordering.html)
20:38 baffle_ joined #salt
20:40 Antiarc_ joined #salt
20:41 amcorreia joined #salt
20:41 ashmckenzie_ joined #salt
20:44 KingJ joined #salt
20:44 smkelly_ joined #salt
20:45 manfred joined #salt
20:45 MeltedLux_ joined #salt
20:45 garphy`aw joined #salt
20:54 ilbot3 joined #salt
20:54 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.6, 2016.11.5 <+> Support: https://www.saltstack.com/support/ <+> 1st Salt Cloud Working Group meeting June 1st, 2017 https://goo.gl/o2OK49 <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic <+> We are volunteers and may not have immediate answers
21:00 park joined #salt
21:02 kojiro joined #salt
21:02 kojiro joined #salt
21:05 freelock joined #salt
21:13 park joined #salt
21:14 buskatoon joined #salt
21:16 buskatoon joined #salt
21:18 buskatoon #salt
21:19 buskatoon joined #salt
21:20 buskatoon joined #salt
21:21 hackel joined #salt
21:21 benjiale[m] joined #salt
21:21 gomerus[m] joined #salt
21:21 toofoo[m] joined #salt
21:21 jerrykan[m] joined #salt
21:21 Jon-Envisioneer[ joined #salt
21:21 ThomasJ|m joined #salt
21:21 theblazehen joined #salt
21:21 saintaquinas[m] joined #salt
21:21 fujexo[m] joined #salt
21:27 buskatoon joined #salt
21:30 absolute- Ah cool
21:31 absolute- I like that rewbycraft
21:32 rewbycraft absolute-: I don't work for saltstack. I'm just a guy who happens to know where to find (some) stuff in the documentation.
21:32 rewbycraft So thank them
21:33 rewbycraft (For having good documentation)
21:34 buskatoon joined #salt
21:41 tom29739 joined #salt
21:44 edrocks joined #salt
21:45 saltsa joined #salt
21:51 Coco_ joined #salt
21:52 Coco_ left #salt
22:22 Bock joined #salt
22:27 afics joined #salt
22:29 swa_work joined #salt
22:35 absolute- Yeah, I just like how it is
22:36 ahrs joined #salt
22:43 brousch joined #salt
22:44 kojiro left #salt
22:44 kojiro joined #salt
22:46 kojiro joined #salt
22:47 kojiro test
22:49 kojiro the first time I run salt-ssh, even if it's just `salt-ssh --help`, it takes several seconds
22:49 kojiro on my Mac, it takes 12 seconds each time, even to just do `salt-ssh --help`
22:49 kojiro does anyone else have this experience? I'm using salt-ssh 2016.3.5 (Boron)
22:56 oida joined #salt
23:06 dxiri joined #salt
23:07 ssplatt joined #salt
23:11 v12aml joined #salt
23:36 Praematura joined #salt
23:38 Felgar joined #salt
23:53 jeddi joined #salt
23:55 Yamazaki-kun joined #salt

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary