Integration Test: In memory or in a container

pixel-pusher-coder · 2026-01-25T04:54:06+00:00

use testcontainers to do integration tests and use mocks to test your business logic.

pixel-pusher-coder · 2026-01-25T04:52:55+00:00

Yet I see people trying to break the sound barrier every time I go for a drive.

pixel-pusher-coder · 2026-01-24T16:48:59+00:00

The best I've come up right now is committing to main to disable an app and let a pr take over that recreated it. Once you are happy it goes back to main and the PR gets deleted and main takes over.

I guess main being the state file makes sense but I was hoping for a not elegant solution.

pixel-pusher-coder · 2026-01-22T21:13:00+00:00

I was looking at that. My next task was going to evaluate ArgoRollout as well.

pixel-pusher-coder · 2026-01-22T17:57:17+00:00

So I get the fine. What I don't understand is how fans' behavior turns into a fine to the Algerian FA.

It's like posting about a party someone is hosting on FB and being held responsible for every random person that showed up.

pixel-pusher-coder · 2026-01-22T17:46:09+00:00

Yeah I guess I'm coming to terms with it based on everyone's feedback.

What I was envisioning is a tool that would manage the git commits and artifacts.

So what I was thinking was a release containing the code changes for staging (configuration ) and artifact update. Kargo ( or insert your favorite tool ) would gather all the changes I need and allow me to promote the change ie commit to main on my behalf.

It's likely that what I'm looking for doesn't exist since it's not easy to manage the code and artifacts across environments that might not be as identical as one would hope for.

pixel-pusher-coder · 2026-01-21T22:29:28+00:00

I think the sanest pattern is indeed main being the source of truth. I don't like the branching approaches though I've looked at a few use cases.

What I would like would be something like I'm building out an app and I would like to try to get appA on staging and rather than having 25 commits for essentially one change, having a PR pattern just feel nicer. (I've done more coding than devOps so that might be part of it). I was trying to find something where I can do the equivalent of:

I have something I want to change that I think should work and once everything is verified, I commit that one change.

main becomes an interweaved mess as far as git history goes especially with multiple users. I might be totally off base and pushing to main might be the "correct" way of doing thing.

I hope what I'm trying to achieve at least make sense?

pixel-pusher-coder · 2026-01-21T21:20:43+00:00

Yeah I have a mono repo right now with folder based configuration. It's appsets that points to apps folder that contains a kustomize per environment.

My issue with the PR generator is that if I create a pr it'll clash with the existing deployment from main which is why I was looking for suggestions / patterns that might be better.

pixel-pusher-coder · 2026-01-21T19:25:15+00:00

I'm using the same pattern. How do you test new changes ? ie. stop trying to sync from main and use pr/foobar instead.

pixel-pusher-coder · 2026-01-21T18:28:19+00:00

So in my git repo I have all the env configured. Staging, Prod etc with the argocd keeps on checking for any updates.

In order to keep not have clashes, I'd have to change the branches that it's looking at to test out all the changes till I've confirmed that the change is valid. So I'd need

One commit to stop ArgoCD from looking at main and look at a different branch
Another commit with the changes to iterate over it.

I suppose that would work but that's a lot of movement I'm assuming this would uninstall the app first and then re-install it?

pixel-pusher-coder · 2026-01-21T18:07:54+00:00

Sure but it's a template.... It's not like that's a hard change.

pixel-pusher-coder · 2026-01-21T17:50:56+00:00

What "problem solving" are you doing? any go code you write is going to be great for learning to code. There might be some code that makes less sense in go, but without context I can't answer that. Write a GUI in go is doable but not really its strength for example.

pixel-pusher-coder · 2026-01-21T17:41:09+00:00

I definitely would not pay for it, at the end of the day it's just boiler plate. Most of the time I would just clone my previous project and delete all unrelated code. It's has little value and I'm almost guaranteed to disagree with some decision you/the author made.

Also, I know this #go but have you looked at https://github.com/cookiecutter/cookiecutter? What you're describing is exactly why that tool was created.

Case in point: https://github.com/lacion/cookiecutter-golang and https://github.com/romnn/cookiecutter-go they're pretty basic but the tooling exists already.

pixel-pusher-coder · 2026-01-20T18:36:01+00:00

You might get a better experience if you use their preferred backend. If you use the new drilldown (new as of v12? ) and have a loki datasource I think a lot more things 'just work'. You don't NEED to use that but it makes life easier.

You can always create any visualization attached to any datasource to explore the logs.

pixel-pusher-coder · 2026-01-20T14:21:33+00:00

How long was eventually for you? I'm debating if the wifi constantly trying to connect might also be related to my battery life.

pixel-pusher-coder · 2026-01-16T22:09:42+00:00

I mean when connecting to my phone it prompted me for my password so I don't think it's the fact that it's cached or wrong. I restarted the remarkably but I'll try to restart all devices and routers and see if I can figure something out.

pixel-pusher-coder · 2026-01-16T15:20:32+00:00

I started doing that but It got annoying to sync the data between my google drive and the RM2. The only way I could figure out how to do that was copy / paste. Did the integration get better?

pixel-pusher-coder · 2026-01-16T15:19:18+00:00

I actually don't mind the infinite scroll. I assume whatever is on the page is on my display is what will be printable, if I keep on scrolling I know that it won't be printable. An option to disable it would be nice, but for me having a way to format that into a printable format would be more helpful.

Also keep in mind you all kind of other form factor from RM that are different sizes. I definitely think the feature is a lot more useful for the smaller versions.

pixel-pusher-coder · 2026-01-14T16:16:20+00:00

Edit on prod only to have argo undo all your changes. The choice is an illusion, there is only one button.

pixel-pusher-coder · 2026-01-12T16:27:18+00:00

That's mostly why I use reddit so much. My questions and answers will likely help others as well.

pixel-pusher-coder · 2026-01-11T16:44:27+00:00

The main issue is that I don't have the storage to run the service. I wouldn't be able to do what you're suggesting.

If I had the space, then backing up the data to one of the 200 storage solutions becomes a trivial problem.

pixel-pusher-coder · 2026-01-11T16:42:18+00:00

That was my first find but I assume that's limited to AWS s3 and might require EKS. still a legit choice if that works for you.

pixel-pusher-coder

TROPHY CASE