lucky me, this "easier" reads landed on a hectic week, but I'm still enjoying it. Today adding jobs from a github repo. This seems really important when sharing jobs with different teams in a centralized hub. #100daysofNautobot 18/100

Another quite easy read today. Job approvals, seems like a nice option to prevent critical devices to be manipulated without a peer review. #100daysofNautobot 17/100

TIL how to interact with nautobot's API. Pretty convenient to get information stored in nautobot. I played a bit with json so I could give a bit of format to the data as well.
#100daysofNautobot 15/100

Today was somewhat easy, but interesting nonetheless! Hook jobs seems super interesting to update devices after changes on nautobot in real-time, or notifications on non-intended changes as well! #100daysofNautobot 14/100

Long day today. Luckily I unintentionally advance yesterday on the next task haha, so today was easy. Pretty cool to execute this commonly repetitive task in one click! #100daysofNautobot 13/100

So... today has been the most interesting. I wanted to do a bit more than just the intended challenge and it was hard. For sure need to read the jobs structure docs! I failed a lot but got it working at the end so overall a good experience 😀 #100daysofNautobot 12/100

TIL to create jobs that can manipulate configs on a device. The example was only a vlan, but the way this can be improved into full configs seems amazing! #100daysofNautobot Day11/100

After a long heavy day, I managed to do an extra #100daysofNautobot . TIL connecting to remote devices from a job execution in nautobot. This particular job I can see great use cases in prod for initial validations as an example! Day10/100.

TIL, well not much on Nautobot, but lots on docker😂 Had some troubles deploying containerlabs in a different host from nautobot and then trying to connect them, but after 2h, everything is setup! #100daysofNautobot Day9/100

TIL how to leverage python libraries to enhance the functionality of jobs in nautobot. I want to tinket a bit with this particular example some more. #100daysofNautobot Day8/100

TIL data validation techniques embedded in nautobot. It can be extremely useful to filter unnecessary data or ensure we have the required data before running a job.

#100daysofNautobot Day7/100

TIL about jobs variables. Interesting way to provide the user the ability to input different values that then can be used by the backend of nautobot. #100daysofNautobot Day6/100

TIL how to use DjangoORM. Pretty intuitive and easy to use, I can see some great use cases at a scale. I'm eager to find out more of the available functions. #100daysofNautobot Day5/100

TIL how to add logging options and user input to new jobs. This could be a great feature when needing to do some tshooting for sure. Will try to squeeze more "Days" later today 😀 #100daysofNautobot Day4/100

Today on #100daysofNautobot I learned how to create and install a new job in nautobot. Amazing feature and really easy to use. Another thing I learned by chance is that apt-get can be used in a docker container to install new packages 😀 Day3/100

Today on #100daysofNautobot I went over nautobot jobs, mostly focused on what a job is and running a pre-installed job that exports records from nautobot as CSV. It came out empty as I ran it on my new nautobot instance, but seems like a really interesting bit to use in the future. Day 2/100

Today I started the #100daysofNautobot. While day one recommends to use Github's codespaces, I decided to go with a docker installation, and to no one surprise I ran into some issues 😅 Fixed now. Beware of poetry version compatibility + docker group permissions. Day 1/100

First, I got me this notebook so I can track every goal and task for next year. Still figuring out smaller details, but here we gooo.