If you gather_facts, which is enabled by default for playbooks, there is a built-in variable that is set called ansible_user_id that provides the user name that the tasks are being run as. You can then use this variable in other tasks or templates with {{ ansible_user_id }}. This would save you the step of running … Read more
This is actually possible to do using SASS maps instead of variables. Here is a quick example: Referencing dynamically: $colors: ( blue: #007dc6, blue-hover: #3da1e0 ); @mixin colorSet($colorName) { color: map-get($colors, $colorName); &:hover { color: map-get($colors, #{$colorName}-hover); } } a { @include colorSet(blue); } Outputs as: a { color:#007dc6 } a:hover { color:#3da1e0 } Creating … Read more
If you’re coming from C/C++, it might also be helpful to think of it basically like this: // Rust C/C++ a: &T == const T* const a; // can’t mutate either mut a: &T == const T* a; // can’t mutate what is pointed to a: &mut T == T* const a; // can’t mutate … Read more
It avoids having to declare all the variables for the returns values. It is called the blank identifier. As in: _, y, _ := coord(p) // coord() returns three values; only interested in y coordinate That way, you don’t have to declare a variable you won’t use: Go would not allow it. Instead, use ‘_’ … Read more
Remove the colon : from the second statement as you are assigning a new value to existing variable. myArray = […]int{11,12,14} colon : is used when you perform the short declaration and assignment for the first time as you are doing in your first statement i.e. myArray :=[…]int{12,14,26}.
You have an extra double quote at the end, which is adding it back to the end of the string (after removing both quotes from the string). Input: set widget=”a very useful item” set widget set widget=%widget:”=% set widget Output: widget=”a very useful item” widget=a very useful item Note: To replace Double Quotes ” with … Read more
Yes, you can use the define keyword to declare a multi-line variable, like this: define ANNOUNCE_BODY Version $(VERSION) of $(PACKAGE_NAME) has been released. It can be downloaded from $(DOWNLOAD_URL). etc, etc. endef The tricky part is getting your multi-line variable back out of the makefile. If you just do the obvious thing of using “echo … Read more
There’s no difference – they mean exactly the same (in GNU Make and in POSIX make). I think that $(round brackets) look tidier, but that’s just personal preference. (Other answers point to the relevant sections of the GNU Make documentation, and note that you shouldn’t mix the syntaxes within a single expression)
It comes ultimately from mathematics: the summation notation traditionally uses i for the first index, j for the second, and so on. Example (from http://en.wikipedia.org/wiki/Summation): It’s also used that way for collections of things, like if you have a bunch of variables x1, x2, … xn, then an arbitrary one will be known as xi. … Read more
Reading the docs I find the section Passing Variables On The Command Line, that gives this example: ansible-playbook release.yml –extra-vars “version=1.23.45 other_variable=foo” Others examples demonstrate how to load from JSON string (≥1.2) or file (≥1.3)