Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2018-05-01

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

All times shown according to UTC.

Time Nick Message
00:00 onslack joined #salt
00:02 stooj joined #salt
00:32 dxiri_ joined #salt
01:12 stooj joined #salt
01:13 MTecknology Edgan: You keep saying networkmanager, but I have yet to see it installed anywhere..
01:14 MTecknology also, ya... that was my issue. I manage what winds up in resolve.conf using /etc/network/interfaces. It was causing configs to be thrown away.
01:39 JacobsLadd3r joined #salt
01:56 ilbot3 joined #salt
01:56 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2017.7.5, 2018.3.0 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic, and https://saltstackcommunity.herokuapp.com (for slack) <+> We are volunteers and may not have immediate answers
02:52 bluenemo joined #salt
03:16 tiwula joined #salt
03:16 swa_work joined #salt
03:18 Deliant joined #salt
03:22 Laogeodritt joined #salt
03:25 zerocoolback joined #salt
05:19 sauvin joined #salt
05:25 stooj joined #salt
05:27 dxiri joined #salt
06:18 chesty joined #salt
07:03 sh123124213 joined #salt
07:16 pppingme joined #salt
07:27 orichards joined #salt
07:46 aT_ joined #salt
08:02 DanyC joined #salt
08:14 DanyC joined #salt
08:29 viq joined #salt
08:55 xet7 joined #salt
08:59 Mattch joined #salt
09:11 sjorge joined #salt
09:13 arlyon joined #salt
09:16 zulutango joined #salt
09:25 Hybrid joined #salt
09:29 evle1 joined #salt
09:38 stooj joined #salt
09:46 arlyon Hey I'm experimenting with salt but for some reason though the master service is enabled in systemctl it fails to start at boot, citing "salt-master.service start operation timed out. Terminating". Starting it again manually works just fine. Running CentOS, latest version of salt from yum. Any ideas what could be causing this?
10:00 joshin joined #salt
10:04 Hybrid joined #salt
10:05 sjorge joined #salt
10:06 Miuku Perhaps /var/log/salt/master and journalctl -b -u salt-master might give you some hints.
10:08 dendazen joined #salt
10:09 arlyon there's nothing relevant in the master log (timestamps don't match)
10:09 arlyon the only output from journalctl is essentially what I wrote earlier
10:10 arlyon "salt-master.service start operation timed out. Terminating." and then "Failed to start The Salt Master Server" followed by "Unit salt-master.service entered failed state."
10:10 Miuku Could it be that it's trying to bind to the network interface but it's not up yet?
10:11 arlyon I'll have a look
10:11 Miuku I don't run CentOS but as I recall it used NM, perhaps you could try adding it as a dep.
10:16 arlyon it's configured after network.target so we'll see if network-online.target helps
10:25 mauli joined #salt
10:32 arlyon no dice unfortunately
10:32 arlyon and there are absolutely no logs
10:38 Elsmorian joined #salt
10:51 netcho joined #salt
10:51 netcho joined #salt
10:56 AngryJohnnie joined #salt
10:56 Elsmorian joined #salt
11:00 darix joined #salt
11:05 viq do you have any external pillars defined?
11:07 viq systemctl list-dependencies salt-master
11:11 viq Ah, and systemctl list-jobs
11:11 viq Except they're not here anymore...
11:16 arlyon joined #salt
11:17 viq Say I have stateA, stateB and stateC, all 3 of them are to run in order, and additionally I want to start running stateA on minion2 only once stateB finished on minion1, and stateA on minion3 only once stateB finished on minion2. How can I do this?
11:21 onslack <netcho> orchestration?
11:22 viq Anything more specific? I looked, but didn't figure out yet what the configuration would look like
11:22 onslack <netcho> <https://docs.saltstack.com/en/latest/topics/orchestrate/orchestrate_runner.html#more-complex-orchestration>
11:24 cswang joined #salt
11:25 viq Hm, so something like 2A having require: salt: 1B ?
11:28 onslack <netcho> correct
11:31 viq Thank you, I'll read more and try playing with it
11:32 pbuell_ joined #salt
11:45 evle joined #salt
11:51 motherfsck joined #salt
11:59 motherfsck joined #salt
12:00 eseyman joined #salt
12:09 briner joined #salt
12:20 mchlumsky joined #salt
12:28 zerocoolback joined #salt
12:55 NEOhidra joined #salt
12:59 pbuell_ joined #salt
13:00 justanotheruser joined #salt
13:11 crux-capacitor has anyone tried using S3 as an external job cache?
13:11 racooper joined #salt
13:22 Valfor joined #salt
13:22 Valfor joined #salt
13:33 zerocoolback joined #salt
14:00 LostSoul joined #salt
14:10 racooper joined #salt
14:17 cgiroua joined #salt
14:17 DammitJim joined #salt
14:23 pbuell_ joined #salt
14:34 gmoro joined #salt
14:37 pbuell_ joined #salt
14:41 karunamon joined #salt
14:41 XenophonF freaking epel-formula, man
14:42 karunamon hiya folks - wondering if there's a sane way to deploy the current development release of salt for production use.. I just upgraded to 2018.3 and am getting bitten by the rsa key issue
14:42 XenophonF what's the rsa key issue?
14:43 viq karunamon: maybe check out pipenv?
14:43 karunamon https://github.com/saltstack/salt/issues/46868
14:43 viq Alternatively, there's a bunch of solutions for "get stuff from pip, output system package"
14:44 karunamon the only thing I'm worried about is whatever ubuntu-specific junk was done in the packaged version that won't carry over
14:45 karunamon granted it can't be worse than it is now since i've got about 900 minions offline, but still :P
14:47 cswang joined #salt
14:47 viq FWIW I'm currently running saltmaster from pipenv on archlinux, to get a newer/more controlled set of auxiliary libraries
14:48 viq Though that's my own infra, with a single digit number of minions :P
14:48 karunamon looking into that now.. really I only need something to get back online until 2018.3.1 drops, which looks like it'll be any day now
14:49 zerocoolback joined #salt
14:52 XenophonF yikes
14:52 karunamon or, instead, I could perhaps just read the patch and apply the like 5 lines fix.. ye gods
14:52 karunamon i always feel like an idiot after i stop by here to ask questions for some reason :P
14:54 karunamon https://github.com/saltstack/salt/commit/a44c356233232fbbe1db5ae00daa6f71ac01715b.patch
14:54 viq karunamon: https://rubberduckdebugging.com/ :P
14:55 karunamon ^ yeah. I was stressing out all weekend about this for no good reason.
14:56 cro joined #salt
15:02 gh34 joined #salt
15:03 pcn gtmanfred: I got your ping.  I was hoping I could ask you some questions here before making that PR too messy
15:04 gtmanfred sure
15:05 pcn So if the slack engine is started by a minion, it can still invoke runners?
15:06 gtmanfred via saltutil.runner it can
15:06 pcn I am not familiar with running an engine in the context of a minion, so it's new territory for me
15:07 cswang joined #salt
15:07 gtmanfred because you want to use pillars, and master processes do not have pillars, you have to run it in the context of a minion, which means you will have to do some other things to make it work
15:07 gtmanfred but without this change, then running the master as a non root user gets broken, because Caller client wants to talk to /etc/salt/pki/minion
15:08 viq As I discovered ;)
15:08 pcn So the PR currently doesn't invoke saltutil.runner, it's just salt.runner.
15:09 gtmanfred it is just injecting runner modules into the engine with `__runners__`
15:10 sjohnsen joined #salt
15:12 pcn That's the in main listen loop, but there's also the get_jobs_from_runner which invokes salt.runner.RunnerClient.
15:12 gtmanfred ahh, you should still be able to use that if running as a minion
15:12 gtmanfred anything that doesn't use `__runners__` should still work
15:13 pcn OK, got it.
15:14 gtmanfred that is the only difference, because if __role == minion, we do not pass in runners into the loade
15:14 gtmanfred r
15:14 pcn That's very interesting.  Well, if you want I'll give it a LGTM, but I'd like to test it out of course :)
15:15 gtmanfred https://github.com/saltstack/salt/blob/2017.7/salt/engines/__init__.py#L28
15:15 gtmanfred yeah, go for it
15:15 pcn All of our engines current run under the master, I wasn't aware that it could be done under a minion so there's a bit of mindblown.gif
15:15 gtmanfred lemme know if it breaks anything else for you, and I will make sure those changes get in before the other way is broken
15:15 pcn viq: are you using the slack engine?
15:16 orichards joined #salt
15:16 gtmanfred yeah, he opened the issue that i am fixing
15:17 gtmanfred well, he is trying to use it
15:17 twill joined #salt
15:19 viq pcn: trying to, I wasn't successful it making it cooperate yet
15:19 pcn I'm not familiar with running the saltmaster as non-root.  Is that a thing now?
15:19 gtmanfred it has been a thing for a long time
15:20 gtmanfred https://docs.saltstack.com/en/2017.7/ref/configuration/nonroot.html
15:20 viq I think I've been doing that since 0.17 days ;)
15:21 gtmanfred also, the other problem with just instantiating a caller client, without specifying opts, is if someone is using `root_dir` or `config_dir` it will fail, because the minion config could be somewhere other than /etc/salt/minion
15:22 viq After changing permissions so master can access /etc/salt/pki/minion I got this error https://pbot.rmdir.de/1VsXpTTYGlrYa0mJBlOI5Q
15:23 pcn Yes, there's a certian amount of *WFM* *shrug* in getting this made. Those caveats would be helpful in the documentation and are difficult to contextualize.
15:23 __number5__ joined #salt
15:23 gtmanfred yeah, they are all just elsewhere in the docs, and come with some of the just experience working on salt.  It def should have been caught in the review process though
15:24 cswang joined #salt
15:25 pcn Good to know.  I mean, I dropped a few hundred lines that completely changed everything about a module that not many peole use.
15:25 gtmanfred heh
15:26 nixjdm joined #salt
15:27 pcn And I would really like for these features to be used in other chat modules, because things like aliases, default targets, etc. are necessary to take some of the sharp corners off of using salt via chat.
15:27 gtmanfred yes
15:29 pcn Also, I must say that there is a weird pillar bug that comes up with the module as it is - changes to pillars will sometimes just never show up.
15:29 pcn I mean to the engine.
15:30 pcn Ugh, late night last night, and I'm not explaining myself clearly.
15:31 pcn And no, I'm wrong.  That's not related to this engine, that's related to a runner we have that also doubl-dips into the master and the minion.
15:32 haam3r joined #salt
15:32 egilh joined #salt
15:33 LostSoul joined #salt
15:33 ksa joined #salt
15:33 flexd joined #salt
15:36 exarkun joined #salt
15:39 Nahual joined #salt
15:41 cswang joined #salt
15:42 viq pcn: feel free to poke me to try things, though it's my own playground so may take me some time to be able to do that
15:42 MajObviousman joined #salt
15:49 tiwula joined #salt
15:53 pcn Thinking about this, is there any reason to allow this to run in the master context at all now?
15:54 onslack <gtmanfred> plenty of people are not using groups_pillar_name
15:55 cswang joined #salt
15:55 pcn OK, that's a reason.
16:07 mchlumsky joined #salt
16:07 cswang joined #salt
16:09 pbuell_ joined #salt
16:13 miruoy joined #salt
16:23 Hybrid joined #salt
16:27 cswang joined #salt
16:31 DammitJim joined #salt
16:36 viq So with running (slack) engine from minion, signal path becomes slack->minion->master instead of slack->master, right? Does that change anything?
16:36 onslack <gtmanfred> it does not
16:37 onslack <gtmanfred> because before it was actually `slack ->; master ->; master`
16:38 viq Thank you
16:39 viq So I just need to move the engine config to minion's pillar?
16:39 cswang joined #salt
16:40 pcn I believe that's right
16:45 netcho .
16:48 Hybrid joined #salt
16:49 AngryJohnnie joined #salt
16:51 onslack <gtmanfred> i am not sure if you can put the full engine config into pillars
16:55 arlyon joined #salt
16:56 cswang joined #salt
16:57 gh34 joined #salt
17:01 arlyon joined #salt
17:03 dxiri joined #salt
17:14 exarkun joined #salt
17:15 cswang joined #salt
17:16 pocketprotector left #salt
17:21 JacobsLadd3r joined #salt
17:26 arlyon_ joined #salt
17:29 cswang joined #salt
17:33 viq Which parts I can't?
17:49 onslack <gtmanfred> like, engines: blah
17:49 cswang joined #salt
17:49 onslack <gtmanfred> you can put the group information into pillars and reference it with the groups_pillar_name
17:49 onslack <gtmanfred> but you cannot put the whole engine config into pillars
17:50 onslack <gtmanfred> <https://github.com/saltstack/salt/blob/2018.3/salt/minion.py#L1130>
17:50 onslack <gtmanfred> it just passes self.opts into start_engines
17:50 onslack <gtmanfred> and start engines does not pull anything from there to pass in the config to starting the engine process <https://github.com/saltstack/salt/blob/2018.3/salt/engines/__init__.py#L20>
17:51 JacobsLadd3r joined #salt
17:52 miruoy joined #salt
17:53 DanyC joined #salt
17:53 armyriad joined #salt
17:54 DanyC joined #salt
17:54 viq Thank you. Shame, I prefer to try and avoid local config.
17:55 viq ...what? "PermissionError: [Errno 13] Permission denied: '/etc/salt/minion.d/engines.conf'" in *master* logs
17:57 mrBen2k2k2k_ joined #salt
17:59 cswang joined #salt
18:00 stooj joined #salt
18:05 Trauma joined #salt
18:08 onslack <gtmanfred> probably a bug that engines default to logging to master log file, because they were by default only for masters.
18:08 onslack <gtmanfred> s/default/originally/
18:12 cswang joined #salt
18:15 viq I don't believe I restarted the minion yet for it to notice the new file - and minion is running as root
18:16 viq https://github.com/saltstack/salt/issues/47418
18:18 onslack <gtmanfred> ahh yes, that one isn’t going to change, the masterminion needs to be able to read the config files in that directory.
18:19 viq ...the what?
18:20 onslack <gtmanfred> MasterMinion, it is a minion inside the master that allows the master to run minion commands, basically a stripped down minion that doesn’t need to connect to the master to do things, and runs with all the same configs, it is very similar to running salt-call --local, except the Masterminion doesn’t have pillars
18:21 viq huh, what's it's use?
18:21 viq reactors?
18:21 onslack <gtmanfred> it does a lot of things, you would have to go code diving to find out exactly what
18:22 viq I don't mean exactly, more like "what are some examples of why it exists"
18:22 onslack <gtmanfred> i don’t have any examples
18:22 viq OK, thanks
18:23 onslack <gtmanfred> looks like reactors, and using returners as ext_job_cache on the master
18:24 viq argh, running salt-master from pip since on arch it has issues with the slack library, now that I moved slack engine to minion I need to run minion from pip...
18:24 viq Thank you :)
18:26 dendazen joined #salt
18:27 cswang joined #salt
18:27 Morrolan joined #salt
18:41 viq {%- for host, ip in salt['publish.publish']('*', 'grains.get', 'external_ip').iteritems()|sort -%}   complains about "Jinja variable 'dict object' has no attribute 'iteritems'" - what's the proper way to do it?
18:41 LotR joined #salt
18:41 onslack <gtmanfred> .items()
18:42 onslack <gtmanfred> iteritems is a python2 thing, and was deprecated in jinja a while ago
18:42 viq Ah, thank you
18:44 JacobsLadd3r joined #salt
18:48 sjohnsen joined #salt
18:51 ooboyle can i have a python2 master and a python3 minion/
18:51 onslack <gtmanfred> yes
18:52 ooboyle thx
18:52 ooboyle when i run pkg.insdtall salt-minion to a windows machine, the minion version pushed is py2
18:52 ooboyle how do i get it to push py3?
18:54 bluenemo joined #salt
18:54 onslack <gtmanfred> you would need to check the winrepo to see if it even offers the py3 version in there
18:54 whytewolf https://github.com/saltstack/salt-winrepo-ng/blob/master/salt-minion-py3.sls
18:54 ooboyle got it
18:54 ooboyle didn't think of that
18:54 AngryJohnnie joined #salt
18:55 ooboyle indeed, there's a py2 and py3 version
18:55 ooboyle but it seems like there's a virtual package named salt-minion that defaults to py2
18:56 whytewolf salt-minion = py2, salt-minion-py3 = py3
18:56 viq https://pbot.rmdir.de/Q7El70hwnW_PB_Ugoe3ZMQ  what am I doing wrong? "TypeError: sequence item 0: expected str instance, list found"
18:56 exarkun joined #salt
18:56 ooboyle i see a salt-minion-py2.sls and a salt-minion-p3.sls
18:56 ooboyle no salt-minion.sls
18:56 ooboyle but pkg.install salt-minion somehow points to py2
18:57 whytewolf ooboyle: look IN the files
18:57 ooboyle sigh. now you're just being smart again...
18:57 ooboyle thx
18:59 cswang joined #salt
19:15 viq test
19:15 cswang joined #salt
19:16 onslack joined #salt
19:16 onslack <gtmanfred> it may take a second for the bot to reconnect
19:17 onslack joined #salt
19:17 onslack <gtmanfred> @msmith I think i fixed the bug in the slack bot
19:18 Trauma joined #salt
19:25 briner joined #salt
19:28 zer0def joined #salt
19:39 cookielord joined #salt
19:44 ooboyle joined #salt
19:47 cswang joined #salt
19:48 LotR joined #salt
19:56 DammitJim joined #salt
20:02 druonysus joined #salt
20:04 pjs_ joined #salt
20:06 pjs_ left #salt
20:07 pjs joined #salt
20:10 Elsmorian joined #salt
20:12 ooboyle I just upgraded a minion to 2018.3.0 py3. I have a custom grain that worked in py2. I converted it to py3 and appear to have worked out the bugs. Except the return doesn't create the grain. But the variable in the return has the data
20:12 ooboyle grains['test_grain'] = test_grain
20:12 ooboyle this worked in py2
20:13 ooboyle if I print(test_grain) in py3, it prints the correct data
20:13 ooboyle what am I missing?
20:14 onslack <gtmanfred> put in a log message and make sure you see it getting run in /var/log/salt/minion?
20:16 ooboyle you know, i put in some custom errors but they aren't printing. i do see one in the log file you noted
20:16 ooboyle thanks. will dig further
20:18 rivyn joined #salt
20:18 cswang joined #salt
20:20 ooboyle hmm, no that was an old log entry. will keep loking around. it's probably something simple
20:26 brejoc[m] joined #salt
20:27 rivyn Hey guys, I'm trying to figure out an appropriate requisite to use (I think).  Here is a simple SLS that I'm having trouble with:  https://ghostbin.com/paste/kenf4
20:27 rivyn I thought that the require in the second state would make it only apply when the first one also did something besides returning clean
20:28 rivyn however, if I start the service manually, and re-apply the state, it ends up not reinstalling, but it stops the service anyways.
20:28 rivyn What should I be using instead?
20:31 arlyon joined #salt
20:31 whytewolf rivyn: https://docs.saltstack.com/en/latest/ref/states/requisites.html#requisite-overview look at this matrix and see if it helps you
20:35 cswang joined #salt
20:37 rivyn whytewolf: I've looked through the requisite docs, but I can't seem to get this working.
20:37 rivyn I've tried onchanges in place of require, but the result is the same.
20:38 rivyn I figured I must not have the same idea of what constituted a "change" in salt's eyes
20:39 rivyn I guess in this state I could just merge the two blocks into one and not need any requisite, but I'd like to understand them better
20:40 whytewolf it should be onchanges.
20:40 whytewolf it needs a module name
20:41 rivyn actually, in a standalone form, it looks like it works, it's when I include it in another sls that there's a problem
20:41 rivyn let me paste some more info
20:42 * whytewolf really does not have the time right now
20:45 rivyn whytewolf: my apologies, I mixed up two different state files and was editing the wrong one! :(
20:45 rivyn onchanges works as hoped
20:46 rivyn sometimes just going through the effort of forming up a detailed paste is enough to shed light on what the issue is. :)
20:47 whytewolf good to hear :)
20:47 * whytewolf buys rivyn a rubber duck
20:48 ooboyle whytewolf yep... something simple... helps if you actually return the thing you want to return... sorry to both you
20:50 relidy joined #salt
20:51 rivyn ooboyle: sounds like we're in similar boats :P
20:51 ooboyle sigh
20:52 * whytewolf tosses rubber ducks around the room
20:53 MTecknology I'm writing haproxy states. I don't need a rubber ducky, I need gin.
20:54 * whytewolf hands MT some everclear and a bunch of juniper berries.
20:54 * MTecknology chews on the berries and takes a couple swigs
20:57 * zer0def koolaids in, quacking loudly
21:02 DammitJim joined #salt
21:03 DammitJim how do you guys deal with upgrading/updating salt on minions?
21:03 DammitJim I mean... I'm doing my Ubuntu updates/upgrades and the system asks if one wants to keep the current minion config or if we want the new one
21:03 DammitJim I'm saying keep old (since I have so much stuff customized)
21:03 MTecknology that's one reason to use .d directories..
21:03 DammitJim is this something that I need to create a state for and deploy the new config with what I need?
21:04 DammitJim MTecknology, that's an AWESOME suggestion!
21:04 whytewolf well I try to avoid as much in the minion config as i can anyway. and use /etc/salt/minion.d for anything i can't avoid in config
21:04 MTecknology "in config" means pillar, ya?
21:05 whytewolf opps yes,
21:05 whytewolf basicly anything i can not put into pillar to avoid it going into a config file
21:06 whytewolf such as anything that actualy deals with the stability of connecting to a master
21:06 DammitJim I'm forgetting, but does the default minion config have a master defined?
21:06 whytewolf DammitJim: 'salt'
21:06 DammitJim now that I think about it, that's the only line that needs to be updated on most of the servers
21:06 DammitJim so, that's not something you can configure in minion.d/myconfig, right?
21:06 viq it is
21:06 whytewolf it is and i do
21:07 viq you can also play with DNS to not have to configure it
21:07 DammitJim oh, even though it's already found in minion?
21:07 viq Also you can pass -A to bootstrap script and it'll do it for you
21:07 DammitJim I don't like playing with DNS... then my team gets lost because we are doing too many tricky things
21:07 whytewolf the "default" /etc/salt/minion file is all commented out
21:07 viq DammitJim: if you have search domain defined, then just salt.yoursearchdomain will work
21:07 DammitJim whytewolf, thanks for clarifying!
21:08 DammitJim so, it says: #master: salt
21:09 DammitJim oh wait... the /etc/salt/minion has nothing configured? everything is commented out?
21:09 whytewolf yes # is the comment line :P
21:09 viq DammitJim: yup, commented out. So, assuming you have dammitj.im and all your servers are told to look for addresses in that domain, if you had an address salt.dammitj.im then you wouldn't need to configure anything on the minions.
21:10 DammitJim whytewolf, I meant other options besides master ;)
21:10 DammitJim then I have no problem here... I'll leave it the way it is
21:10 DammitJim because the "newer" minion file has nothing that I need
21:11 whytewolf same with the master file
21:12 whytewolf it tells you what the defaults are. in the config but everything is commented out
21:12 DammitJim thanks guys
21:12 DammitJim I was making a problem out of a problem that never existed
21:27 cswang joined #salt
21:42 Rubin joined #salt
21:44 cswang joined #salt
21:46 arlyon joined #salt
22:10 cswang joined #salt
22:10 rivyn can requisites be used on an include:?
22:17 arlyon joined #salt
22:21 Rubin joined #salt
22:22 ecdhe joined #salt
22:22 MTecknology rivyn: In what way would you combine an include and requisite?
22:23 rivyn I was thinking include:\n  - blah.blah\n  - require:\n    - some.state
22:23 rivyn just wondering if I can conditionally include
22:24 MTecknology you can conditionally include, yes... but what you're describing now doesn't seem to make sense
22:24 rivyn I only want the include to be processed after a particular state
22:25 MTecknology that's not going to happen
22:25 rivyn or maybe sometimes with onchanges, only if a state actually does something.
22:25 rivyn why not?
22:25 MTecknology What is your actual goal?
22:25 rivyn I thought I just described it pretty well
22:25 rivyn I can paste up an example
22:25 MTecknology that could prove useful
22:26 Trauma joined #salt
22:26 rivyn MTecknology: https://ghostbin.com/paste/pnymx  <-- I want to only remove the service account, after the packages that depend on it are removed
22:27 rivyn not the best example, as order probably isn't relevant in this case
22:27 rivyn but you get the idea
22:27 MTecknology that's no the job of include, that's the job of requisites
22:27 MTecknology not*
22:27 rivyn but I want to use a common include file
22:27 MTecknology that doesn't change anything
22:28 rivyn so that's what I'm asking - how to apply requisites to the include
22:28 MTecknology you don't
22:28 MTecknology you apply them to states
22:28 rivyn ah I think I understand the confusion.
22:28 rivyn I have two different package scripts like this
22:28 rivyn that both use the same service account
22:29 rivyn so I can't add a requisite in the included sls for either one of them specifically.
22:29 rivyn it could be either one.
22:29 MTecknology re-read the requisites documentation...
22:29 rivyn hah, I've read that page more than I think any other salt docs :P  what should I look for?
22:30 MTecknology I not-so-secretly suspect you skimmed instead of read that page or it would probably be pretty obvious..
22:30 ECDHE_RSA_AES256 joined #salt
22:31 MTecknology Oh, neat. I wonder how long we've had <req>_any. :)
22:31 rivyn I've read it quite a few times in fact.  It's hard for me to comprehend.  You can call me stupid, but not a liar...
22:32 rivyn it's just difficult for me to grasp
22:32 MTecknology You know what you're problem is.. there's an entire set of requisites that cover that scenario.
22:33 MTecknology s/set/class/ ?
22:33 rivyn I got it now.  I just need a little help sometimes comprehending the docs, sorry to be a bother.
22:34 whytewolf MTecknology: <req>_any came in 2018.3
22:36 MTecknology rivyn: what solution did you find?
22:37 MTecknology whytewolf: Another awesome new feature that I don't get to make use of. :(
22:38 cswang joined #salt
22:38 rivyn require_any, I'm assuming.  I'll try it out in a bit.
22:38 rivyn oh, it's for 2018.3 only
22:39 rivyn so I probably didn't just not comprehend that before
22:39 rivyn we're still on 2017.7
22:39 MTecknology What does require_any do?
22:39 rivyn on 2017.7, nothing.
22:39 rivyn :P
22:40 MTecknology k.. what's it do?
22:40 rivyn what I just asked about?
22:41 rivyn it'd be a lot clearer if you could just be a little helpful, but nevermind.  I'm sorry to have been a bother.  I'll dig into it more when I have time and try to figure it out.
22:41 whytewolf well, with require all of the states listed have to succeed. require_any. then only 1 of them has to succeed. the rest could fail.
22:41 MTecknology Did you see me comment about <req>_any looking neat and just assume that was your magic answer?
22:41 rivyn I thought you were addressing my question, yes.  I apologize.
22:42 MTecknology blindly guessing...
22:42 Rubin joined #salt
22:42 rivyn well, I'm really not very competent with this stuff, and trying my best to figure it out.  I'm sorry if that is offensive to you, I really don't mean that.
22:42 rivyn cheers.
22:43 MTecknology what a gnat..
22:45 Trauma joined #salt
23:05 cswang joined #salt
23:09 dendazen joined #salt
23:26 netcho joined #salt
23:53 cswang joined #salt
23:58 mavhq joined #salt

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