Welcome to the warmup exercise for the Why Am I podcast called “the Fantasy Restaurant.” In here, my guests get to pick their favorite: drink, appetizer, main, sides, and dessert…anything goes. Jimmy is a meat and potatoes kinda guy, and while his menu isn’t exotic, it’s a good choice any day of the week. I hope you enjoy this meal with Jimmy.
Help us grow by sharing with someone!
Please show them some love on their socials here:
https://www.youtube.com/jimmydiresta
https://jimmydiresta.com/
https://www.instagram.com/jimmydiresta/?hl=en
If you want to support the podcast you can do so via https://www.patreon.com/whyamipod (this gives you access to bonus content including their Fantasy Restaurant!)
Hey everybody, I’m Greg Sowell and this is Why Am I, a podcast where I talk to interesting people and try to trace a path to where they find themselves today. My guest this go around is Andy Kay. This individual is one of LA’s finest Private Investigators, but he may not be what you expect. Not only does he travels the world helping his clients, but he also takes certain cases very personal…much the way I think I might. After everything he’s done and seen, I figured he’d be pretty jaded, and while he does have a healthy dose of skepticism, he still sees the good in the world, and it seems he tries to embody that good himself. I hope you enjoy this chat with Andy.
Help us grow by sharing with someone!
Please show them some love on their socials here:
https://www.facebook.com/kayandainvestigations/
https://www.instagram.com/KAinvestigates/
If you want to support the podcast you can do so via https://www.patreon.com/whyamipod (this gives you access to bonus content including their Fantasy Restaurant!)
Hey everybody, I’m Greg Sowell and this is Why Am I, a podcast where I talk to interesting people and try to trace a path to where they find themselves today. My guest this go around is Jayse OBrein.This fella is a man of many talents: he’s a voice over artist, an over the top foodie, an actor, reactor, and costco dad. What strikes me the most about Jayse is his insanely high energy, his obvious zest for life, and the way he wants to bring everyone along with him. There’s some definite parallels between the two of us, and I’m not just talking about our love for 90s pop culture, though I feel this might be the most important one. At any rate, I hope you enjoy this fast paced conversation with Jayse.
Help us grow by sharing with someone!
Please show them some love on their socials here:
https://www.instagram.com/jaysetagram/?hl=en
https://stan.store/ObrienMedia/p/get-my-guide-now-cu4avwts
If you want to support the podcast you can do so via https://www.patreon.com/whyamipod (this gives you access to bonus content including their Fantasy Restaurant!)
Hey everybody, I’m Greg Sowell and this is Why Am I, a podcast where I talk to interesting people and try to trace a path to where they find themselves today. My guest this go around is Patrick Christmas. Imagine combining soccer, football, and frisbee…that is kind of the foundation of ultimate frisbee. Now add in quick action, full field hucks, and insane layout catches, and you might start to get an idea of why this ultimate vet decided to single handedly start an Austin ultimate pro team. If you’ve never watched a game, pop to youtube and give it a watch, then grab tickets for your local team. At any rate, I hope you enjoy this conversation with Patrick.
Help us grow by sharing with someone!
Please show them some love on their socials here:
If you want to support the podcast you can do so via https://www.patreon.com/whyamipod (this gives you access to bonus content including their Fantasy Restaurant!)
Hey everybody, I’m Greg Sowell and this is Why Am I, a podcast where I talk to interesting people and try to trace a path to where they find themselves today. My guest this go around is Jimmy Diresta. Jimmy is the first maker, a term I believe he really popularized, I started watching on youtube. I think maker isn’t just a moniker, or even a life style for Jimmy…I think he truly has no other choice…I think it’s part of his soul…or as he describes it, the reason he’s here. From the moment we started talking Jimmy was my cousin who he hasn’t seen for a minute, and I hope you all enjoy catching up with Jimmy.
Help us grow by sharing with someone!
Please show them some love on their socials here:
https://www.youtube.com/jimmydiresta
https://jimmydiresta.com/
https://www.instagram.com/jimmydiresta/?hl=en
If you want to support the podcast you can do so via https://www.patreon.com/whyamipod (this gives you access to bonus content including their Fantasy Restaurant!)
There are three module types that can be either imported or included which are: import/include_task, import/include_role, or import/include_playbook.
While these are mostly the same there are some subtle differences…so subtle in fact that I couldn’t really figure out what the difference was, so why not share what I’ve learned 🙂
So the textbook difference between the two is that:
Import is static. This means they are fully loaded before playbook execution begins.
Include is dynamic. This means they are parsed during execution as they are reached.
I’m not sure how this reads to you, but my understanding was that variables and the like would be interpreted strangely for imports…kind of like whatever the value of a variable was at load would somehow dictate their inclusion or reaction…which was wrong. Here’s a playbook I wrote to try and test:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | # playbook.yml
---
- name: A demo on using include vs import in Ansible with incorrect info
hosts: localhost
gather_facts: false
vars:
testvar: "Initial Value" # Initial value for the variable
tasks:
- name: Display initial testvar value
ansible.builtin.debug:
msg: "Before import_tasks and include_tasks: testvar is {{ testvar }}"
- name: Use import_tasks (static)
import_tasks: tasks/import-tasks.yml
- name: Update testvar to "Updated Value"
set_fact:
testvar: "Updated Value"
- name: Use include_tasks (dynamic)
include_tasks: tasks/include-tasks.yml
- name: Re-run import_tasks after update
import_tasks: tasks/import-tasks.yml |
Here are the two task files it calls(really they are just spitting out debug info…nothing special here):
1 2 3 4 5 | # tasks/import-tasks.yml
- name: Import Task Display testvar if it is "Updated Value"
ansible.builtin.debug:
msg: "Import Task: testvar is {{ testvar }}"
when: testvar == "Updated Value" |
1 2 3 4 5 | # tasks/include-tasks.yml
- name: Include Task Display testvar if it is "Updated Value"
ansible.builtin.debug:
msg: "Include Task: testvar is {{ testvar }}"
when: testvar == "Updated Value" |
I was thinking that in the above example it wouldn’t run any of the imports(as at runtime the variable would have been set incorrectly). Take a look at the job output, though:
1 2 3 4 5 6 7 8 9 10 11 12 | PLAY [A demo on using include vs import in Ansible with incorrect info] ********
TASK [Display initial testvar value] *******************************************
ok: [localhost] => {
"msg": "Before import_tasks and include_tasks: testvar is Initial Value"
}
TASK [Import Task Display testvar if it is "Updated Value"] ********************
skipping: [localhost]
TASK [Update testvar to "Updated Value"] ***************************************
ok: [localhost]
TASK [Use include_tasks (dynamic)] *********************************************
included: /runner/project/tasks/include-tasks.yml for localhost
TASK [Include Task Display testvar if it is "Updated Value"] ******************* |
I tried all kinds of variations, but no matter what, I couldn’t get it to fail. It ignored the first import as one would expect, but when I reset the variable it went ahead and ran the second import…So, I surrender trying to make it functionally display their differences. There are a few things that are definetly different as per this documentation:
Using include* does have some limitations when compared to import* statements:
Using import* can also have some limitations when compared to dynamic includes:
Looking at the plus’ and minus’ of each, just go with include by default.
Most of the shortcomings of include are things I never run into, so not really a problem.
The shortcomings of import are much more impactful: not being able to use it with loops and losing inventory source variables.
Conclusion
In short, use include and just ignore the import stuff.
If you have any other topics of interest, let me know. If you would tweak or tune this, drop me a note on that too.
Good luck out there; happy automating, and happy including!
Welcome to the warmup exercise for the Why Am I podcast called “the Fantasy Restaurant.” In here, my guests get to pick their favorite: drink, appetizer, main, sides, and dessert…anything goes. Gary puts together a meal that seems to incorporate a lot of the foods found near his NY home…and Asia, and Greece, and Italy LOL. Though it varies a lot, it all sounds delicious. I hope you enjoy this meal with Gary.
Help us grow by sharing with someone!
Please show them some love on their socials here: https://twitter.com/GaryGoldsteinLA, https://www.instagram.com/garygoldsteinla/, https://www.garygoldsteinla.com/book-please-come-to-boston.
If you want to support the podcast you can do so via https://www.patreon.com/whyamipod (this gives you access to bonus content including their Fantasy Restaurant!)