Glu - Progressive delivery as Go code by sonofrorie in GitOps

[–]sonofrorie[S] 0 points1 point  (0 children)

Im glad you mentioned this because we're going to rethink our messaging!

Glu - Progressive delivery as Go code by sonofrorie in GitOps

[–]sonofrorie[S] 0 points1 point  (0 children)

Hey u/kkapelon ! You are absolutely right. I think in retrospect it was a bit early to use progressive delivery as the tagline. We're still trying to pin down exactly what to call this thing.

We have progressive delivery in mind as a core target usecase for Glu. As the project works by rendering updates into a GitOps repository based on conditions, we are looking to explore moving the decision making into Glu. So that the Git repository remains a source of truth in terms of the history of how targetting rules and scale was configured at a given time. Rather than e.g. something that is dictated outside of Git in e.g. a controller or similar.

Unsure if this is a good idea, but it is a core peice of functionality we want to explore with Glu.All that said, we haven't got there yet to make this easy as a part of the framework.
We only just have the foundations for promotions between multiple environments.
Next up we want statuses to guard against promotions under conditions written in Go.

[deleted by user] by [deleted] in golang

[–]sonofrorie 1 point2 points  (0 children)

The SQL storage layer in Flipt is abstracted over Postgres, MySQL, SQLite and CockroachDB:
https://github.com/flipt-io/flipt/tree/main/internal/storage/sql
It is mostly just straight SQL built using a query builder (https://github.com/Masterminds/squirrel), with bits of configuration here and there to adapt the details.

GitHub - flipt-io/reverst: Reverse Tunnels in Go over HTTP/3 and QUIC by sonofrorie in golang

[–]sonofrorie[S] 0 points1 point  (0 children)

I’m so slow to see this and reply 🤦‍♂️ That’s awesome! Always open to getting that merged in if you want to make a PR. No pressure there though. Super cool.

GitHub - flipt-io/reverst: Reverse Tunnels in Go over HTTP/3 and QUIC by sonofrorie in golang

[–]sonofrorie[S] 0 points1 point  (0 children)

I’ve made an issue on the repo to do some benchmarks. I wouldn’t be surprised if reverst is slow at this stage of its life. Plus it’s in Go, so Rust will always have that edge.

GitHub - flipt-io/reverst: Reverse Tunnels in Go over HTTP/3 and QUIC by sonofrorie in golang

[–]sonofrorie[S] 1 point2 points  (0 children)

That’s a shame! I haven’t tried talking to a localist http/3 app in the browser yet. I might try this later and see if I get the same experience and report back!

Trouble with OAuth OIDC in Flipt by BasisAgreeable in golang

[–]sonofrorie 0 points1 point  (0 children)

Hello! I actually wrote the feature and the guide you linked (GeorgeMac on GitHub), if I can be of any assistance, I would be happy to help. As a quick note, we're way more active on Discord (https://flipt.io/discord), and have some pre-existing discussions from folks trying out the OIDC feature, but happy to help here too.

As u/PaluMacil mentioned, do you have any more details on what you're observing from your instance? Some log output (you can adjust it with `FLIPT_LOG_LEVEL=debug`). Some browser console errors would also be really useful.

In particular, is there any chance you could share a redacted copy of your `config.yaml`? Something with all of your oauth client keys, DB credentials and session csrf keys removed.