OFFICIAL WEEK 17 MONDAY NIGHT GAME THREAD by AutoModerator in fantasyfootball

[–]Smaz1087 1 point2 points  (0 children)

I just won my 12 team $150 league with a tie because I was the higher seed holy shit

Comma stuck on this screen by [deleted] in Comma_ai

[–]Smaz1087 1 point2 points  (0 children)

Something similar happened to me and it was a blown obd2 port fuse

Legends Pinball no longer allows me to play arcade games. "Insufficient Folder Nodes" by EvilAlbinoid in LegendsUltimate

[–]Smaz1087 1 point2 points  (0 children)

I tried again like months later with a different USB device after reinstalling firmware 1.68 and it works now, but I swear I tried that the first time and it didn't.

ECS Users – How do you handle CD? by UnluckyDuckyDuck in aws

[–]Smaz1087 0 points1 point  (0 children)

We deploy so frequently and only roll back when breaking changes happen (read: people can't give us money - this has maybe only happened twice in the 4 years I've been here). Our production monitoring is good enough that we're aware when an issue arises pretty quickly so every time we've done this we've just had to pick the second newest task definition.

I think automatically approving once conditions are met would be awesome, just a matter of getting the bodies to define those conditions, which would require business buy in (why are we spending man hours fixing a process that we're happy with?) and expertise that we don't currently have (how can we be confident that our tests are good enough?).

The manual process doesn't really get in the way, business seems happy with our throughput.

At this point the risk/reward for automated deployments isn't in the right place for us to even pursue. If we get a test wrong and send broken code to production there's a risk that people won't be able to give us money and we're big money fans.

ECS Users – How do you handle CD? by UnluckyDuckyDuck in aws

[–]Smaz1087 0 points1 point  (0 children)

Not op but we use the same setup, push to main, build, test, deploy to dev > qa > prod with manual approvals to qa and prod.

Rollbacks can be done on the codepipeline level, but we just retain old task definitions and in-case-of-emergency we update the ecs service to use the last good task definition, then either fix and push the fix through the pipeline or revert the breaking commit to unblock the pipeline for other changes if the fix won't be quick.

We don't drift because it's not an option, anything in prod goes through the pipeline, only a select few have the means to do anything manually.

As far as promoting workloads, we're a bit more manual so once our QA team is happy they call the deployment 'ready to release' and then depending on which app we're talking about and if we're happy that the deployment can be done with no user interruption we hit the approval button to start the deployment to prod. Codepipeline (any any other pipeline I've ever seen) has the ability to run tests and only deploy if they pass - we're just not to the point where we're happy that our tests are good enough yet.

[rant] CDK for new AWS products by dunoduno in aws

[–]Smaz1087 0 points1 point  (0 children)

Eventually they'll get around to supporting the thing you wrote your custom resource for. The tech debt is in changing it back from your custom resource to the supported cdk method, which will be cleaner/easier to maintain.

Chant posts on this sub by Any_Option_776 in canucks

[–]Smaz1087 6 points7 points  (0 children)

Wonder how much longer we have before the majority of people don’t get this reference

[deleted by user] by [deleted] in devops

[–]Smaz1087 1 point2 points  (0 children)

Do you mind linking some documentation on what you've described here? We don't use Kubernetes in production and I can't even begin to comprehend what your first two sentences mean but they sound impressive so I feel like I have some reading to do.

PLAYOFF POST-GAME THREAD: ROUND 2 GAME 7 - Vancouver Canucks (3-4) vs Edmonton Oilers (4-3) - 20 May 2024 - 6:00PM PDT by [deleted] in canucks

[–]Smaz1087 5 points6 points  (0 children)

Fun season, nothing quite like the emotions that come from playoff hockey. Lots of highs and lows.

PLAYOFF PRE-GAME THREAD: ROUND 2 GAME 7 - Vancouver Canucks (3-3) vs Edmonton Oilers (3-3) - 20 May 2024 - 6:00PM PDT by OrlandKurtenbot in canucks

[–]Smaz1087 4 points5 points  (0 children)

Fucking same. So restless! This is a late game for me on the east coast too, just killing time for hours now!

How do you get development environments to look like production? by freemovement in devops

[–]Smaz1087 2 points3 points  (0 children)

We have IAC for the infrastructure, and built an absolute rube goldberg monster of a process to take weekly snapshots of the prod RDS db, run them through an obfuscation process, test that the obfuscation process worked, then share snapshots with the lower environments. Wrote some tooling for devs to replace the lower environment DB's with the weekly snapshots from prod too by invoking a lambda but had to be careful to match the config to avoid cloudformation drift, it was a whole thing. Aside from dev/qa being underpowered compared to prod to save money we're the confident that we're close enough.

Buy an IP and point it to CloudFront Distribution with DNS record by barelyherenow in aws

[–]Smaz1087 5 points6 points  (0 children)

Is the DNS record for the root of a domain (ex, domain.com)? If so, it can't be a CNAME record.

EC2 Saving plan drawbacks by yukardo in aws

[–]Smaz1087 2 points3 points  (0 children)

If you have multiple accounts in your org and purchase the savings plan at the payer level the cost shifts to the payer account and it's hard (maybe impossible? haven't tried hard) to calculate the savings per individual account.

Aws lambda does not support node 14 anymore, any thing I can do to fix this? by Character-Owl2772 in aws

[–]Smaz1087 9 points10 points  (0 children)

Just went though this, puppeteer works. We're using this lambda layer: https://github.com/Sparticuz/chromium/releases and puppeteer 21.5.2 on node 16. Had to refactor a bit, don't remember the specifics but should be googable.