DevOps

OpenTF fork (prepare for alpha) is now available at the GH Repository here:

https://github.com/opentffoundation/opentf

Take a look at the issues tab to see some of the live RFCs and discussions happening. Lots of things like the use of tf in the binary/name and bring their own registry.

TLDR: terraform bad, pulumi good

https://opentf.org/announcement

Is your organization doing anything to ensure new devs are productive from day one? How do you guys handle local environments for the code you are working on? I am trying to get my company to enable teams to create their own workstation image that contains all the dev tools and local application-related infrastructure needed for that team to be productive. Has anyone done something similar?

Both are valuable, but which should be the priority? Assuming finite hours in a day, how much time should be spent working on your actual work vs. learning about the customer vs. learning about technology you haven't worked with before?

Here's a hypothetical scenario at a company: We have 2 repos that builds and deploys code as tools and libraries for other apps at the company. Let's call this lib1 and lib2.

There's a third repo, let's call it app, that is application code that depends on lib1 and lib2.

The hard part right now is keeping track of which version of lib1 and lib2 are packaged for app at any point in time.

I'd like to know at a glance, say 1 month ago, what versions of app is deployed and what version of lib1 and lib2 they were using. Ideally, I'm looking for a software solution that would be agnostic to any CI/CD build system, and doubly ideally, an open source one. Maybe a simple web service you call with some metadata, and it displays it in a nice UI.

Right now, we accomplish this by looking at logs, git commit history, and stick things together. I know I can build a custom solution pretty easily, but I'm looking for something more out-of-the-box.

Won't impact most users apparently.

Hey guys. Curious about how you run your automated tests.

I've playing a bit with openSLO in past few weeks. Really interesting stuff when applied to the development pipeline. I tought I'd share my perspective on this in a small blog post.

Hello,

TL:DR Atmospheric scientist with knowledge of cli, python want change to a SRE job

Let me explain my background, I am M.Sc in atmospheric science with a few publications in the field, during my studies I work most of my time working with cli tools so I am confident with shell and cli tools, pipelines, stdout, stderr, tmux, etc. I worked using numerical model that you need to compile, this teach me tools like makefiles, modules and cronjobs to did it operational. I have experience with python and other scientific languages like R, Matlab. During my free time took some course of docker. Even I set up a Nginx webpage that I leave to die for lack of time or setup a raspberry pi to download "linux isos" using docker.

I really enjoy the automation of process, and help other colleagues to setup and install the environment to work.

I know my lack of networking, monitoring, and I'm not sure if my self taught skills (science standards) are comparable with a CS worker.

I want to learn or get the certification needed to get a SRE job to mid 2024.

Any advice, course or certication to help me to get in the road?

Seems to be back up now, still waiting for information on the cause, so far have the vague reason "config change" from the GitLab issue linked

I use terraform fairly extensively in my role, and saw terraform cdk seems to be a nice extension to terraform. Unfortunately it’s convert feature hasn’t seemed to work for me and I’m hesitant to rewrite everything by hand.

Has anyone been using cdktf and enjoying it enough that could convince me to do that rewrite?