Determinsitic Connection Strings
Hi All! I am investigating using Neon as a source for pull preview DBs combined with ArgoCD. I saw the blog post about how to do it with ArgoCD but I’m wondering if there may be a more deterministic way. Is there anyway to guess what the connection string will be if we know the branch name ahead of time? That way we could inject the url in the app set vs needing to connect to argocd from GitHub actions.
2 Replies
foreign-sapphire•2y ago
@Riker unfortunately not. This does make it a bit tricky to use with Argo CD. We did hack on an operator to experiment with adding CRDs to manage some of the branch provisioning and connection strings as k8s Secrets, but it's not prioritized right now: https://github.com/evanshortiss/neon-kube-operator
GitHub
GitHub - evanshortiss/neon-kube-operator
Contribute to evanshortiss/neon-kube-operator development by creating an account on GitHub.
genetic-orangeOP•2y ago
@ShinyPokemon thanks! Definitely aware it’s a bit of a niche use case and request but would be something I’d happily pay for as an addon. Some type of static random url between branches suffixed with branch name or git has
Hash*