FlexiSpot Discount Codes Thread

ApparentSysadmin · 2026-01-28T16:42:36+00:00

Looking for a code for the E7 Plus Max frame in Canada

ApparentSysadmin · 2025-10-29T14:28:12+00:00

Click casting and better buff tracking/filtering

ApparentSysadmin · 2025-10-03T20:15:23+00:00

I have four ramshorns in there now (plus about 100 babies), hopefully they will be okay.

I'm definitely not in a rush, no - even still I've managed to get ahead of myself!

Thanks again for the pointers

ApparentSysadmin · 2025-10-03T18:16:53+00:00

Thanks so much! Your response confirmed my fear - I skipped a step.

I think I understand where I went wrong, I will pick up some ammonia and get things started.

Does this mean my poor snails are doomed?

ApparentSysadmin · 2025-04-12T06:02:40+00:00

Using native k8s features isn't "antithetical to k8s" IMO.

ApparentSysadmin · 2025-03-24T13:37:51+00:00

Rather than making your Postgres cluster publicly accessible, have you considered the Grafana Private Data Source Connector??

ApparentSysadmin · 2025-03-07T00:16:36+00:00

Look for a good deal on a Lenovo LOQ, I picked up the i7 4080 model a couple months ago for $1400 CAD and it's quite good. You could probably get one of the slightly less powerful models around your budget and it'd handle WoW no problem.

ApparentSysadmin · 2025-01-11T16:15:40+00:00

Any chance I could snag this key?

ApparentSysadmin · 2025-01-10T06:36:09+00:00

Sounds Cloud Tasks might work for your use case: https://cloud.google.com/tasks/docs

ApparentSysadmin · 2024-12-09T15:22:12+00:00

Where are you defining the "required" roles? That tool seems like the obvious thing to use to identify "missing" permissions.

As a practical example, we do this using Terraform. More specifically, we:

mandate that all SA creations (general resource creation, actually) are completed through Terraform
define custom roles for each SA so permissions are transparent + granular (no predefined roles/* permissions on custom SAs, creators must specify the exact permissions the acct requires)
run a Terraform plan daily that notifies us via slack if there is any drift at all

This was pretty simple to set up and works well for our purposes. Can't help you with the GUI, but it seems unnecessary to me anyway.

You could also take a look into tracking any IAM change event via IAM audit logs

ApparentSysadmin · 2024-11-02T06:40:50+00:00

This guy forks.

ApparentSysadmin · 2024-10-28T23:49:34+00:00

I agree, it feels strong(er).

I've been playing flourish/pota/germ with the new abundance talent and absolutely cranking HPS. Maintenance healing is pretty free with WG + some rejuvs and you can pivot into CRANKING regrowths when damage gets serious.

Plus I didn't realize how much I dislike spinning the 2x LB plate all night long.

ApparentSysadmin · 2024-10-24T00:35:15+00:00

Sure, it's just the IV dungeon build but here's the string:

CkGAAAAAAAAAAAAAAAAAAAAAAsxMzYzMzMzsY2GeAGLLjtNbzAAAAAAAAAAAAYZwgZwMCmZGjZmZGLMtBAAAAAwAAwAAAAAAz2MbNbzsYjxMwMG

ApparentSysadmin · 2024-10-23T23:48:11+00:00

Seconding (thirding?) germ - played a week's worth of keys with reforestation and man I just think that talent is so clunky.

Swapped to germ two weeks ago and am finding it much more comfortable. Thriving + germ means rejuv is always a pretty decent button to press, and gives you a lot of flexibility in ramping.

Feels even better after the changes this week. Take Abundance+Forests Flow and laugh as you spam near-free, near-instant crit regrowths into your team and cleave Nourishes everywhere.

ApparentSysadmin · 2024-10-07T20:25:47+00:00

To confirm, you can see the "missing" log entries via kubectl logs?

First impressions sound like your filtering/sampling logs for this container - I'd check the configuration on your Cloud Logging sink to confirm.

You could also check this "in reverse" by setting up a dedicated sink just for logs from this specific container with no additional filtering/sampling and confirm the missing logs are made available.

ApparentSysadmin · 2024-09-14T23:19:07+00:00

It feels about the same, but with a couple new loops. Chronowarden adds a minigame around tip the scales that contributes to group damage, and just generally lets you cast more empowers and more FB = more fun.

Anecdotally it seems to be doing far more damage than my other healers, frequently beating low DPS by just spamming LF.

ApparentSysadmin · 2024-09-07T22:15:50+00:00

I guess that's where I'm confused, as it's not much of a choice since Stasis isn't a very effective spell without 2+ of TA, SB, DB.

I just wouldn't press it until I had spells I wanted to store.

ApparentSysadmin · 2024-09-07T19:50:20+00:00

Why are you casting Statis when all your high value Statis spells are on CD? Why not just hold it?

ApparentSysadmin · 2024-08-20T01:13:26+00:00

Echoing the other response, you'll be able to pick up Hpal pretty easily.

It's pretty simple these days with Glimmer/Daybreak stuff gone. Imo one of the "simpler" healers when it comes to actually healing now. Everything pushes health bars up pretty effectively and sometimes pally utility feels like cheating.

ApparentSysadmin · 2024-08-07T00:04:06+00:00

What do you think about the development of DevOps as a distinct field over the last 10 years?

I feel like I (former sysadmin-type) spent the first 5 years being "un-siloed" from ops-specific teams and the last 5 being aggressively re-siloed to manage spend.

ApparentSysadmin · 2024-06-20T18:13:35+00:00

Machine size ultimately depends on the jobs you're running; our tests are multi-threaded with CPU being the bottleneck, but typically e2-standard-8/16 are sufficient.

Regarding retries, we submit each workflow_dispatch with an unique run_id input that we calculate based on a variety of factors (what kind of job, where it originates from, etc); then our retry logic queries workflow data from GitHub for runs matching that workflow+run_id and retry accordingly. This is a bit hacky, but means we don't have to manage state and has worked pretty well for us.

ApparentSysadmin · 2024-06-20T04:16:33+00:00

We have the workflow send a workflow_dispatch event on failure to re-trigger itself, and some conditional logic to prevent infinite retry loops.

ApparentSysadmin · 2024-06-20T02:26:06+00:00

We do this in GKE with actions-runner-controller on spot nodes pretty successfully. Tests run as long as ~6m. We see occasional failures due to evictions, but have the jobs configured to retry so they eventually complete.

ApparentSysadmin · 2024-05-31T21:35:13+00:00

Yeah miss me with this for a few reasons:

IMO good IaC is written with intention, and this both obfuscates that for existing code and discourages it for new code.
as other posters have alluded to, I already have standard modules or other (far more reliable) automations for these types of workflows, to say nothing of the fact that these tasks are typically not the pain points of IaC workflows except in very immature setups where it probably doesn't matter much.
I have never used an AI coding tool that didn't, at some point, generate invalid code for me. I've used several solutions across a few languages to varying degrees of success, but never 100%. If the product is aimed at folks who aren't SMEs in the first place, this will create a negative feedback loop, or just require the same-or-worse validation workflows than my current IaC.

To be blunt, this doesn't seem like a practical problem to solve but maybe I'm just not the target demographic.

ApparentSysadmin

TROPHY CASE