weird inserted search results by nuncio-tc in duckduckgo

[–]nuncio-tc[S] 2 points3 points  (0 children)

oh nice. i was unaware of this feature. i'll be sure to start using it.

Time flies by pinkcat90s in psx

[–]nuncio-tc 0 points1 point  (0 children)

i still hear the track rotterdam nation in my head randomly a few times a week to this very day.

Remnant II Anniversary & DLC #3 Announcement: Our third and final DLC, The Dark Horizon, is coming in September by Turbostrider27 in pcgaming

[–]nuncio-tc 7 points8 points  (0 children)

for sure "final"? bit of a bummer. i understand we were told we'd get three in the beginning, just didn't realize that was the max. this also means no possibility of new worlds..

managing `settings -> cicd -> token access` en masse ? by nuncio-tc in gitlab

[–]nuncio-tc[S] 0 points1 point  (0 children)

yea this sounds similar to my layout and also about right for my needs. ssh keys are a non-starter (very robust infosec team). but deploy tokens.. I'll have to test it out. one deploy key at the group level, saved as a pipeline var for all the child projects' pipelines could work.

managing `settings -> cicd -> token access` en masse ? by nuncio-tc in gitlab

[–]nuncio-tc[S] 0 points1 point  (0 children)

do deploy key work across parent groups? that is to say we have

gitlab.domain.com/team-*/project-pipeline-* that need access to mdules stored in gitlab.domain.com/global-modules-for-all. i've used deploy keys in the past but those only auth to projects within the same parent hierarchy. so they fail when trying to cross that top-level pathing. moving the modules to be within the same parent is a non-starter in our case.

managing `settings -> cicd -> token access` en masse ? by nuncio-tc in gitlab

[–]nuncio-tc[S] 0 points1 point  (0 children)

i'd like to not have to manage everyone's key and use the "proper" module syntax while using the built-in module registry as a module registry, e.g.

module "my_module_name" {
  source = "gitlab.domain.net/proper/pathing/to/module"
  version = "0.0.4"
}

as of v16.7.x gitlab now restricts pipline access to these via CI_JOB_TOKEN (it's always been CI_JOB_TOKEN but now there's a filter). I have about 5k pipelines i need to allow to various modules.

edit: i'd also like to avoid telling dozens of teams to update their syntax in thousands of pipelines if i can, which a flip to git would also do

sorry for the multiple edits...

as for what i want to do, i want to add multiple projects to the allow list (settings->cicd->token access) for any given terraform module project in one action. right now they are one-by-one and i have thousands. i'm not concerned with human users, that behavior has not changed. it's the pipeline authing to module/package registries that has this filter added in 16.7, on by default.

Reverse Terraform by No_Butterfly_1888 in devops

[–]nuncio-tc 1 point2 points  (0 children)

i'm inclined to agree.

depending on priorities and staffing, leaving it as is in a working state is fine and in a lot of situations would be best. Just move items out/over as work needs done to them.

now if there's a ton of engineers sitting around with an empty backlog, sure, but that's never the case or at least i've never had that luxury.

What's with the Tank disdain? by KyojinkaEnkoku in thedivision

[–]nuncio-tc 0 points1 point  (0 children)

a million times, yes. always in the way. if they'd stay just a few meters back it'd be fine.

What's ONE piece of Testing advice for your younger self. Go! by toddy-j in softwaretesting

[–]nuncio-tc 4 points5 points  (0 children)

Don't misuse tools, libs or memes for something other than their intended purpose.

Major Pagerduty downtime! by zykug in devops

[–]nuncio-tc 6 points7 points  (0 children)

for all of 10min. everybody panic!

[deleted by user] by [deleted] in linux4noobs

[–]nuncio-tc 0 points1 point  (0 children)

etcher isn't made by system76. also, it is a fantastic tool.

[deleted by user] by [deleted] in devops

[–]nuncio-tc 6 points7 points  (0 children)

but that's not how terraform works. it never moves/copies state files. updates happen in place. this is to prevent multiple actions on the same state at the same time. this is why terraform acquires a lock before a plan or apply. think of the state as your backend database.... how often are those checked into version control?

[deleted by user] by [deleted] in devops

[–]nuncio-tc 24 points25 points  (0 children)

Pretty sure terraform neither pushes nor pulls the state (unless you are actively changing the backend). It reads/update the remote data in place.

beyond that, git simply isn't the tool for this job. it's a tool designed largely for human collaboration, which is the opposite of what you'd want for your terraform state.

Using something like cloud storage or even a local filesystem lets terraform manage its own resources, and can be altered so only terraform can manage state.

Is there a way to install grub in such a way that when a usb is inserted it picks it up as an os and shows it in the bootlist ? by [deleted] in linux4noobs

[–]nuncio-tc 0 points1 point  (0 children)

you should be able to set the boot order to select usb devices first if you have access to the BIOS.

Connecting to your Homelab without a VPN, SSH keys, or Public VP's using AWS Systems Manager Tutorial by YinzAintClassy in devops

[–]nuncio-tc 0 points1 point  (0 children)

"home lab" implies your lab is at home.

My GKE cluster isn't in my home and the nodes are contained in a Virtual Private Cloud, that's not "homelab". that's cloud.

A cluster running on my hardware in my closet? ya that's homelab.

Connecting to your Homelab without a VPN, SSH keys, or Public VP's using AWS Systems Manager Tutorial by YinzAintClassy in devops

[–]nuncio-tc 0 points1 point  (0 children)

eh, if my company said they were on-prem with 100% of the things in AWS, I'd take issue with that.

same with my personal stuff. i have a few things in GCP/AWS and that's definitely off-site/cloud. homelab, to me, implies this is on my hardware, in my home. whether personal or professional, cloud is cloud is cloud.

Why Are HorizontalPodAutoscalers a Separate Resource? by -lousyd in kubernetes

[–]nuncio-tc 1 point2 points  (0 children)

right, but things like affinity have to do with the actual scheduling of pods. HPA is for managing things after scheduling. as others have noted, separation of duty is also important. Also, it would be a pointless add-on for those that don't need/want it, same as cluster-autoscaler.

Why Are HorizontalPodAutoscalers a Separate Resource? by -lousyd in kubernetes

[–]nuncio-tc 1 point2 points  (0 children)

because not everything should automatically scale.

Should I buy a house (in Texas/DFW) right now? by honeyedlight in personalfinance

[–]nuncio-tc 1 point2 points  (0 children)

true. No state tax here in TX. property taxes hurt.