More features for our employee account lifecycle automations. The coding isn't as much the hard part as keeping track of all the different moving pieces and how it all interacts.
For example, when using Azure Enterprise App user provisioning to sync data into AD from an HR system, it can only set the Name (separate from DisplayName) property when creating a new user. This limitation isn't documented anywhere I can find, and it doesn't even show as an error in the logs when it tries to update an existing one and fails.
It's the curse of "one man army": this shit is too complicated to keep it all in my head at one time, and also too complicated to bring anyone up to speed in a reasonable time frame. So I'll continue soldiering on with it on my own. Thankfully the end is in sight.
Don't do this sort of shit for any boss that isn't worth it. Mine has no overtime expectations, is very obviously training me to move upward within the team, and each of the last two years I've gotten >10% raises.
I'm trying to get my first bug bounty payout and am gearing up to take a week long certification exam.
Congrats on crushed bug!
Stood up some podman services. Using cloud init to provision the VMs, and podman quadlets to translate docker compose into systemd files. Really solid, just need to make them rootless now.
Also looking at a tailscale deployment for zero trust. The feature set is a lot wider than I thought.
What are you guys working on?
Literally, absolutely nothing. For the first time in weeks. Just enjoying the evening.
I love this for you :)
Guess there is something new!
Code block, work for online retailer so no more deployments or changes through January.
Onto projects, been looking at how we could deploy hoop. dev as a teleport alternative.
Sounds like a great time to test some things in a dedicated test environment. You can break the test environment as much as you like.
Making my home server automatically draw backups from the hosted server. Not hard, but needs to be done.
Also the home server is too loud. But it's idle most of the time. So I would need to enter the bios to change the fan settings. But for that I'd need a GPU that fits in there. So now I have to buy a GPU first just to enter the BIOS once and change the fan settings. I figured it is not possible to change fan settings as root user on Linux?
Are you going to apply this at work?
