Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2018-03-05

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

All times shown according to UTC.

Time Nick Message
00:07 onlyanegg joined #salt
00:15 thelocehiliosan joined #salt
00:23 hemebond joined #salt
00:33 fignew joined #salt
00:34 fignew joined #salt
00:35 smead joined #salt
00:35 fignew joined #salt
00:50 exarkun joined #salt
00:53 zerocoolback joined #salt
01:00 zerocoolback joined #salt
02:17 shiranaihito joined #salt
02:20 hsfh joined #salt
02:25 scarcry joined #salt
02:27 exarkun joined #salt
02:27 smead joined #salt
02:35 zerocoolback joined #salt
02:36 amy_ joined #salt
02:57 ilbot3 joined #salt
02:57 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.11.9, 2017.7.4 <+> 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
03:03 smead joined #salt
03:14 smead joined #salt
03:41 zerocoolback joined #salt
03:42 zerocoolback joined #salt
03:42 zerocoolback joined #salt
03:43 zerocoolback joined #salt
03:44 zerocoolback joined #salt
03:47 evle joined #salt
03:48 JPT joined #salt
03:52 hohum joined #salt
04:07 exarkun joined #salt
04:56 masber joined #salt
05:03 col360 joined #salt
05:11 onlyanegg joined #salt
05:18 LocaMocha joined #salt
05:27 LocaMocha joined #salt
05:46 exarkun joined #salt
06:00 nuhamind2 joined #salt
06:23 Heartsbane joined #salt
06:23 Heartsbane joined #salt
06:25 jkleckner joined #salt
06:40 nuhamind2 joined #salt
06:52 masber joined #salt
06:56 onlyanegg joined #salt
07:06 amy_ joined #salt
07:23 Hybrid joined #salt
07:27 exarkun joined #salt
07:31 amy_ joined #salt
07:33 amy_ joined #salt
07:34 Ricardo1000 joined #salt
07:40 Hybrid joined #salt
07:40 fl3sh joined #salt
07:48 inad922 joined #salt
07:48 amy_ joined #salt
07:50 amy_ joined #salt
07:52 amy_ joined #salt
07:58 amy_ joined #salt
08:03 hoonetorg joined #salt
08:03 amy_ joined #salt
08:06 Pjusur joined #salt
08:17 darioleidi joined #salt
08:18 Tucky joined #salt
08:18 zerocoolback joined #salt
08:26 jrenner joined #salt
08:41 colttt joined #salt
08:48 cyteen joined #salt
08:54 daks joined #salt
08:56 ws2k3_ joined #salt
09:00 ws2k3 joined #salt
09:07 exarkun joined #salt
09:08 mattfoxxx joined #salt
09:08 _maniac_ joined #salt
09:09 froztbyte joined #salt
09:13 cewood joined #salt
09:20 Freeaqingme joined #salt
09:21 wryfi joined #salt
09:25 bdrung_work joined #salt
09:29 fignew joined #salt
09:35 zerocoolback joined #salt
09:35 Dejv joined #salt
09:36 Mattch joined #salt
09:45 justanotheruser joined #salt
10:02 gmoro_ joined #salt
10:08 amy_ joined #salt
10:08 syd_salt joined #salt
10:13 J0hnSteel joined #salt
10:24 cewood joined #salt
10:29 pbandark joined #salt
10:38 Naresh joined #salt
10:42 J0hnSteel joined #salt
10:47 exarkun joined #salt
10:55 mrueg joined #salt
10:59 masuberu joined #salt
11:03 inad922 joined #salt
11:05 smead joined #salt
11:11 J0hnSteel joined #salt
11:23 cewood joined #salt
11:24 pualj joined #salt
11:28 inad922 joined #salt
11:40 GrisKo joined #salt
11:52 Pjusur joined #salt
11:54 inad922 joined #salt
11:55 masber joined #salt
12:02 evle joined #salt
12:09 amy_ joined #salt
12:18 xet7 joined #salt
12:34 bebeszi hello there
12:35 bebeszi i have three git repos with pillar init.sls files
12:35 bebeszi i made a /etc/salt/master.d/pillar.conf file with ext_pillar key and addresses to git repos
12:36 bebeszi what do i have to do next? after refreshing pillars i still don't see new pillars in minions
12:36 bebeszi do I need to specify file_roots and create a /srv/pillar folder with top.sls there?
12:38 onslack <mts-salt> each ext_pillar needs its own top.sls
12:38 onslack <mts-salt> those get resolved individually, and then the resulting dictionaries gets merged into the final pillar
12:39 bebeszi oh
12:39 bebeszi thx
12:40 bebeszi so if my git project is called 'test' and it has init.sls file with few pillar keys
12:40 bebeszi should i make top.sls that goes like
12:40 bebeszi base:
12:40 bebeszi '*':
12:40 bebeszi - test
12:40 bebeszi ?
12:41 bebeszi should i rename init.sls to test.sls?
12:42 smead joined #salt
12:46 bebeszi hm?
12:46 onslack <mts-salt> the top looks right, yes. it's up to you how you structure the content
12:47 onslack <mts-salt> both are valid. folders are generally more useful when their contents are related somehow
12:47 bebeszi okay, thx
12:47 onslack <mts-salt> but having a folder just to put init.sls in it perhaps isn't
12:49 bebeszi mts-salt: so should all the content be in top.sls?
12:51 viq Can I use comparison operators in targeting? '-G saltversion<2017.7.3' for example?
12:59 onslack <mts-salt> bebeszi: top is used to point to which sls files contain pillar data
12:59 onslack <mts-salt> so your example of test.sls is correct
13:00 onslack <mts-salt> viq: you could perhaps use regex targetting, but i don't think there are operators, no
13:01 viq mts-salt: thanks, that's what I ended up doing.
13:03 aanriot joined #salt
13:06 thelocehiliosan joined #salt
13:08 Nahual joined #salt
13:17 tuxawy joined #salt
13:27 yuhl joined #salt
13:29 yuhl left #salt
13:35 _val_ He guys. Here i have a for loop: https://dpaste.de/kJAN/raw  <-- How can I change this so {{ key }}={{ value }}  is part of  file.append key
13:45 zerocoolback joined #salt
14:00 gh34 joined #salt
14:07 sxar joined #salt
14:08 babilen _val_: Which file.append ?
14:08 zer0def _val_: what about this? https://ghostbin.com/paste/tq9ar you can provide either a text blob or a list of strings
14:09 zer0def depending on jinja version, that `{% else %}[]` might not be available for you, though
14:10 amy joined #salt
14:11 exarkun joined #salt
14:13 brokensyntax joined #salt
14:19 bebeszi i have one more question
14:19 bebeszi because right now i have permission denied when git_pillar tries to fetch
14:20 bebeszi but I have configured .ssh/config file correctly for root and ubuntu user
14:20 bebeszi i use 2015.8 version of saltmaster (Beryllium)
14:24 thelocehiliosan joined #salt
14:26 zer0def do you run your salt-master as a non-root user? sounds like a filesystem permission error to me, meaning either lack of read priviledges on ssh private key or lack of write permissions on wherever the daemon's caching your git pillars
14:26 bebeszi i use salt with sudo
14:26 bebeszi so theoretically key reading privileges should be fine
14:27 zer0def ok, so root's credentials are being used
14:27 zer0def are you able to reach all git repos by `sudo git clone`ing?
14:27 bebeszi yeah, and I just put IdentityFile /home/ubuntu/.ssh/id_rsa
14:27 bebeszi in root's config
14:27 bebeszi zer0def: yeah
14:28 bebeszi I have tested the same commands like cloning and fetching when sudo su
14:28 xet7 joined #salt
14:28 bebeszi and worked flawlessly
14:28 _val_ zer0def: ID file.append in SLS cassandra.ddc is not a dictionary
14:28 onslack <mts-salt> you could try checking the debug logs, and if you can't spot anything then pastebin them here. assuming you're using `salt-run git_pillar.update`
14:28 zer0def i'm unsure whether ssh_config is read by salt-master
14:29 onslack <mts-salt> it depends on which git library you're deferring to - gitpython or pygit2
14:29 bebeszi gitpython
14:29 onslack <mts-salt> that should defer to the system ssh command and thus your config. in which case debug logs next
14:29 bebeszi I have the same config for gitfs when pulling recipes
14:29 bebeszi and it works
14:30 _val_ zer0def: wait.. maybe my mistake
14:30 zer0def _val_: sure looks like a yaml dictionary to me, so i'm unsure, would need to run as debug to see how the template is being rendered
14:31 zer0def actually, you probably don't need to run as debug, i just don't remember how you render a template on master's side
14:31 onslack <mts-salt> if it's a state sls then slsutil.renderer
14:31 zer0def how about templates used in `file` state calls?
14:32 onslack <mts-salt> then use the minion to expand it using cp.get_template
14:32 bebeszi oh shit, my mistake!
14:32 bebeszi it was w/o git@ at the beginning
14:32 bebeszi sorry :D
14:32 _val_ zer0def: what does else?
14:33 zer0def _val_: renders when your loop is empty
14:33 _val_ I mean this notation  {%else %}[]{%endfor %}..
14:33 zer0def or, strictly speaking, a false-value (which an empty python list is)
14:34 zer0def mts-salt, would that func differ from `file.apply_template_on_contents`?
14:34 bebeszi okay, pillars are updated with git source, how can I check if they are correctly loaded?
14:35 bebeszi "sudo salt '*' pillar.items" gives me only a hostname
14:35 zer0def bebeszi: as mts-salt mentioned, you might want to run `salt-run git_pillar.update` to refresh
14:35 bebeszi zer0def: done, all seems to be fine with True results
14:35 onslack <mts-salt> pillar.items shows what the master thinks pillar should be, rather than what the minion has loaded into memory
14:36 hohum is there a module like ini but for just plain old configuration files instead of ini files
14:36 zerocoolback joined #salt
14:36 tuxawy joined #salt
14:37 hohum *ini_manage
14:37 onslack <mts-salt> zer0def: that function is used for inline templates i believe, whereas get_template works with template files such as those starting salt://
14:37 hohum ini_manage.options_present is the most useful thing in the world
14:38 hohum if not a bit slow
14:38 onslack <mts-salt> what are "plain old configuration files" ?
14:38 hohum just option=value pairs in a text file
14:38 hohum usually .conf file
14:39 onslack <mts-salt> not that i'm aware of. you'd either need to manage the entire file or some subset of it
14:40 onslack <mts-salt> unless there happens to be a helper already for the particular conf you're using
14:42 hohum I've been using file.replace and regular expressions to mimick what ini_manage does but it isn't as expressive
14:42 hohum or reliable
14:43 hohum I guess it's time to start learning about writing salt modules :)
14:44 masuberu joined #salt
14:44 zer0def there used to be a `DEFAULT_IMPLICIT` ini section keyword, which would put everything underneath it outside of any ini section
14:44 zer0def as far as i can tell, that's no longer there
14:44 onslack <mts-salt> if you can't manage the entire file then file.replace or similar would have been my suggestion
14:47 racooper joined #salt
14:50 hohum I'm okay with using managed files in cases where I have highly custom config (nginx, apache, etc) but for managing a few edits in OS config files, something like a "configuration manager" (IE ini_manage or find.replace) is our preferred method
14:50 hohum for two reasons
14:50 hohum 1) So that anyone with familiarity with the OS' administration tools knows what's going on
14:50 jkleckner joined #salt
14:50 hohum and 2) when you muck around with the OS configs things tend to break when you do upgrades
14:51 onslack <mts-salt> most configs have a conf.d for customisations, does that apply here?
14:51 hohum depends on the OS and distribution
14:52 hohum like RHEL and CentOS is good for that
14:52 hohum FreeBSD, not so much
14:52 onslack <mts-salt> i've not used that so i'm guessing, but i'd be tempted to add one for any config that supports generic includes :)
14:53 onslack <mts-salt> if no includes then you're into block replace-based management
14:54 hohum find.replace is actually pretty good at what it does.   I just don't want to teach my sysadmins about regular expressions :)
14:54 onslack <mts-salt> for example, one state that asserts a file.append with a block end marker and a prereq state to inject the block start marker, and onchanges to a third state to file.block_replace your content
14:55 onslack <mts-salt> there's often more than one way to do things with salt :)
14:55 Shirkdog_ joined #salt
14:55 rawzone^ joined #salt
14:56 onslack <mts-salt> if your people don't know regex already then teaching them would be wise, or they're just sysops rather than sysadmins
14:57 kiorky joined #salt
14:57 hohum yeah it's kind of a throwback to the days where all guys did all day long was look after print jobs and reset passwords ;)
14:58 hohum but I stand by my original statement
14:58 zer0def just be sure to teach them about destructive backreferences while you're at it, so that they don't annihilate your machines by accident
14:58 hohum ini_manage is a more elegant and less error-prone solution
14:58 hohum hehe
14:58 heaje joined #salt
14:59 evle joined #salt
14:59 onslack <mts-salt> all they should need is google and a cheatsheet of phrases to lookup ;
14:59 onslack <mts-salt> ;)
15:00 onslack <mts-salt> oh, and a rubber duck...!
15:00 zer0def as mts-salt mentioned, if your software supports generic .d inclusions, that'd probably be much more preferred, because you could just slap in file.managed and forget
15:01 zer0def trade the rubber duck for a regex tester
15:01 onslack <mts-salt> i don't know a generic method for those that don't, it would have to depend on what part of the config needed to be managed and in what way
15:02 xet7 joined #salt
15:02 Rumbles joined #salt
15:02 nledez joined #salt
15:02 nledez joined #salt
15:03 Rumbles hello people of #salt, just wondering if anyone knew when there would be an 18.04 ubuntu repo added to https://repo.saltstack.com/apt/ubuntu/ ??
15:03 theloceh1liosan joined #salt
15:03 Rumbles I know it's only beta right now, but it's due next month and I would like to start playing around with it now
15:03 smead joined #salt
15:04 zer0def does the 16.04 repo used with 18.04 beta cause problems?
15:04 Rumbles haven't tried, yet, that is probably what I will be doing to be honest...
15:04 zer0def they'd probably be the best way to use the upstream repo, until a 18.04 dist pops up
15:05 zer0def s/they/that/
15:05 Rumbles I just want to get an idea of when all the things I need for prod will be ready for use on 18.04
15:06 Rumbles Since the 16.04 folder was created on 2016-05-24 hopefully it won't be much more than a month
15:06 zer0def have you checked the contents? pretty sure it's as up to date as stability/bugfixes allow
15:07 Rumbles latest was released on 21/02/18 so it's pretty recent, I just wouldn't want to use packages tested against xenial on bionic unless I had to in prod
15:08 zer0def pretty sure you'll be safe, unless some dependency has breaking changes, pretty unlikely
15:09 gtmanfred 18.04 dist will show up for the first salt release after 18.04 has officially been released
15:13 Rumbles ok, cool, thanks!
15:25 cgiroua joined #salt
15:25 amy joined #salt
15:31 nielsk joined #salt
15:31 nielsk joined #salt
15:32 nielsk joined #salt
15:33 masber joined #salt
15:44 jkleckner joined #salt
15:44 pjs joined #salt
15:45 exarkun joined #salt
15:46 nielsk joined #salt
15:48 BitBandit joined #salt
15:49 nielsk joined #salt
15:50 Hybrid joined #salt
15:54 inad922 joined #salt
15:55 nixjdm joined #salt
16:09 Hybrid joined #salt
16:12 ponyofdeath joined #salt
16:18 dkehn joined #salt
16:27 tiwula joined #salt
16:28 fignew joined #salt
16:32 fignew joined #salt
16:37 lordcirth_work I have somehow managed to make diffs work backwards
16:41 doubletwist joined #salt
16:41 thelocehiliosan joined #salt
16:43 edrocks joined #salt
16:51 shoogz joined #salt
16:52 shoogz joined #salt
16:52 shoogz joined #salt
16:58 hasues joined #salt
17:03 edrocks joined #salt
17:05 hasues joined #salt
17:12 amy joined #salt
17:13 RF_ joined #salt
17:22 Nahual left #salt
17:22 Nahual joined #salt
17:23 shoogz joined #salt
17:23 shoogz joined #salt
17:24 shoogz joined #salt
17:24 shoogz joined #salt
17:25 shoogz joined #salt
17:25 shoogz joined #salt
17:27 shoogz joined #salt
17:28 jrj_ joined #salt
17:31 shoogz joined #salt
17:32 shoogz joined #salt
17:33 shoogz joined #salt
17:33 shoogz joined #salt
17:37 shoogz joined #salt
17:37 hasues joined #salt
17:38 shoogz joined #salt
17:38 shoogz joined #salt
17:40 shoogz joined #salt
17:40 shoogz joined #salt
17:40 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.11.9, 2017.7.4 <+> RC for 2018.3.0 is out, please test it! <+> 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
17:41 shoogz joined #salt
17:41 Edgan gtmanfred: What would it take to get the desired error? https://pastebin.com/gSh4e2F1  This problem makes Salt hard to debug. It isn't just true for pillars, but also jinja. It is especially bad when Level 2.1 is something like db, and there is Level1:db, Level2:db, ... .
17:42 shoogz joined #salt
17:44 tuxawy joined #salt
17:47 zer0def Edgan: i'm guessing using the `pillar` context variable is undesirable?
17:49 cgiroua_ joined #salt
17:49 gswallow joined #salt
17:50 zer0def pretty sure i've bumped onto something at some point that allowed you to raise your own jinja exceptions
17:50 gswallow left #salt
17:50 Edgan zer0def: You mean like {{ pillar['Level1']['Level2.1'] }} ?
17:51 zer0def yes, not sure what kind of error that would raise
17:51 Edgan zer0def: same problem
17:51 Edgan zer0def: That is my point. pillars and jinja both throw incomplete errors like this
17:51 wongster80 joined #salt
17:52 RF_ joined #salt
17:52 zer0def i'd probably default to a python false-value and handle it somehow or find a way reraise with clarification
17:52 Edgan zer0def: My theory has been it is the way python or the jinja library work. Then I noticed pillars do the same thing, and it might be unfixable, reasonably, but I want an answer.
17:53 Edgan zer0def: If I can figure out what causes it, maybe I can fix it and make everyone happy
17:53 zer0def without peeking at the code, i'm guessing that's just a reraise of a KeyError
17:53 tuxawy joined #salt
17:54 Edgan zer0def: A KeyError would make sense
17:57 jenlynny joined #salt
17:57 onlyanegg joined #salt
17:59 zer0def Edgan: if worst comes to worst, there are always `fail_with_changes` and `fail_without_changes` functions in `test` state module
18:00 RF_ joined #salt
18:00 RF_ hi
18:02 RF_ I upgraded to 2017.7.4 from 2017.7.3 today and the command I had been running with 2017.7.3 'salt-call --local state.highstate --force-color test=True' stopped working and threw error 'Passed invalid arguments: 'NoneType' object is not iterable.'. Does anyone know what's causing this?
18:02 RF_ it worked perfectly fine with 2017.7.3.
18:02 mavhq joined #salt
18:04 Edgan RF_: tried with -l trace?
18:04 Edgan My first guess is it doesn't have to do with your command line options.
18:07 onlyanegg yeah, RF_, if you can isolate it to one of the states in your highstate that would be helpful
18:07 RF_ Edgan: yeah I did. There were no errors from the parsing
18:10 edrocks joined #salt
18:11 RF_ looks like it's one of the two state files is having issues. I am going to look into it
18:12 zer0def btw, RF_, just out of curiosity, have you tried passing `--force-color` before `state.highstate`?
18:12 Edgan RF_: It is something about your setup. https://pastebin.com/TY096x78
18:12 Edgan zer0def: doesn't matter
18:13 Whissi joined #salt
18:13 zer0def was about to say it *shouldn't* matter
18:13 zer0def just covering bases
18:13 Edgan zer0def: I had the same thought, but replicated his command with the most basic setup.
18:14 Edgan I am also already on 2017.7.4
18:14 Edgan RF_: What do you have set in /etc/salt/minion?
18:15 RF_ Edgan: https://pastebin.com/FVKvqhep
18:17 Edgan RF_: try without the external pillars
18:17 cgiroua joined #salt
18:20 RF_ I tried without the ext_pillar but got the same error
18:22 RF_ Edgan: I was able to narrow down which state file might be causing this by excluding them one at a time. The thing is that show_sls didn't throw any errors with that particular state file.
18:23 Edgan RF_: Can you share the state?
18:25 FroMaster joined #salt
18:26 zer0def RF_: changes are modest, have you tried dumping out `file_client: local` from your /etc/salt/master? https://github.com/saltstack/salt/compare/v2017.7.3...v2017.7.4
18:26 RF_ Edgan: https://pastebin.com/iDJQ8BMQ
18:27 RF_ zer0def: this is a masterless setup so I am running the command on minion
18:27 zer0def there's a small addition to `salt/config/__init__.py`, not sure how it affects things, if at all
18:30 ymasson joined #salt
18:31 Edgan RF_: My guess is  pillar['mount_volumes'] is empty
18:31 Edgan RF_: You are trying to join it in that state
18:33 zer0def that looks appropriate; it also means, i need to step back since i'm being less than helpful
18:33 cewood joined #salt
18:34 Edgan zer0def: It is still a weird error for that problem
18:35 zer0def i wouldn't expect `pillar['mount_volumes']` to be a None, more like rendering errors, but that might be dependent on how jinja filters interact with undefined variables
18:36 Edgan zer0def: I said guess, because it is the only iteration in the state
18:36 zer0def i'm just aligning myself with your hypothesis
18:41 zer0def i'm guessing it might be a badly parsed external pillar, just checked on my end and it coughed up pillar object not having attribute
18:41 Edgan RF_: This seems like a case where you would be better off turning this into a python script to do the whole thing, or use salt modules/state to do this the salt way.  https://docs.saltstack.com/en/latest/ref/states/all/salt.states.mdadm.html   https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.extfs.html
18:42 Edgan RF_: I generally find cmd.runs best avoided, if possible.
18:43 Edgan RF_: Simpler code is more readable code. :)
18:51 sjorge joined #salt
19:06 sjohnsen joined #salt
19:20 edrocks joined #salt
19:21 Trauma joined #salt
19:31 xet7 joined #salt
19:32 schemanic joined #salt
19:32 pcn Anyone got any pros/cons of external pillars
19:34 RF_ Edgan: sorry, I've been in meetings. Thank you so much for looking at it. I didn't even realize there ewas mdadm state. I was just porting our puppet code to salt and didn't event think about checking about the mdadm state.
19:35 RF_ Edgan: I agree 100% on avoiding cmd.runs
19:36 RF_ Edgan: I do have mount_volumes defined in pillar though
19:39 RF_ zer0def: you are correct that `pillar['mount_volumes']` is not None. It's defined in pillar.
19:45 Edgan RF_: I would recreate the state piece by piece and isolate that part that breaks it
19:47 Edgan RF_: Then we can help further
19:48 RF_ Edgan: Ok, I will do that. Thanks!
19:52 tuxawy joined #salt
19:52 xet7 joined #salt
19:53 deuscapturus joined #salt
20:01 xet7 joined #salt
20:13 jkleckner1 joined #salt
20:14 RF_ joined #salt
20:14 RF_
20:14 RF_ quit
20:15 RF_ joined #salt
20:32 rjc joined #salt
20:34 sjohnsen joined #salt
20:37 jkleckner joined #salt
20:38 lordcirth_work Could someone check for me if develop branch file.managed shows diffs with - and + reversed with test=True?
20:38 lordcirth_work Trying to figure out if my commits changed it, for some reason develop won't start for me
20:43 zulutango joined #salt
21:02 pbandark joined #salt
21:03 jrj joined #salt
21:10 RF_ joined #salt
21:12 zella joined #salt
21:12 RF_ I have a state file like this: https://pastebin.com/itL7eP5h . How do I use the "port" variable in the jinja template salt://files/etc/init/dosomething.conf? I just used {{ port }} in it but got "Jinja variable 'port' is undefined" error.
21:12 zella left #salt
21:16 mechleg RF_:  that macro looks ok at first glance, how are you calling it?
21:20 RF_ mechleg: I am calling the macro like this https://pastebin.com/Q2qVvvP9
21:21 mechleg oh, i misread.  you want to use the port variable in the souce of that file.managed, that sounds a bit trickier
21:21 RF_ mechleg: yeah
21:22 RF_ mechleg: is it possible?
21:23 whytewolf RF_: https://gist.github.com/whytewolf/b48db787e38a7288bd31c818de5fae46
21:24 mechleg not sure, but it sounds useful.  lol, i thought it would have somthing to do with context
21:25 RF_ whytewolf: Thank you!!
21:25 whytewolf np
21:25 darioleidi joined #salt
21:49 jeffspeff joined #salt
21:51 ecdhe joined #salt
21:53 DammitJim joined #salt
21:59 om2 joined #salt
22:01 ECDHE_RSA_AES256 joined #salt
22:02 onlyanegg joined #salt
22:11 _xor joined #salt
22:11 __peke__ joined #salt
22:22 onlyanegg joined #salt
22:27 cgiroua joined #salt
22:37 justanotheruser joined #salt
22:43 cliluw joined #salt
23:02 onlyanegg joined #salt
23:12 jkerr joined #salt
23:15 druonysus joined #salt
23:17 masber joined #salt
23:23 masuberu joined #salt

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