11 hours ago
Hi, guys,
I have done my research and I found out that deployment based on release tag has already been the topic of some discussion, but I think this discussion needs to be enriched.
I am a big fan of railway, because it makes my life a lot easier in personal and professional projects. Depending on the deployment philosophy, branch deployment is the way to go. However, for different cases, release tag deployment fits better. I will bring my case.
I have a project that is an auth server (actually a microservice), that is meant to be application agnostic (i.e., does not know any business logic regarding the application) so it can be used in any project.
As the projects evolve, so does my auth server, and sometimes a breaking change comes. When it does, I need to refactor the other services of each project so that the new changes fit in. This is where the problem arises.
Older projects take longer to refactor. If I could use a fixed version until everything is fixed, life would be a lot easier. Could I solve it with a fixed branch? Sure! But then I'd there is the possibility that a new branch needs a specific fix and it gets applied to this branch. Then it starts to drift away from the original project. If we work with release tags, instead, this possibility is gone.
Today I am holding new projects from being deployed because I need older projects to adapt to the newer version of my auth server before I can use it in all projects. It would not happen with release tags.
So this is my side of the story. If I would have to do a CI/CD workaround to make it happen I'd rather get a VPS and work the kubernetes on my own...
0 Threads mention this feature
0 Replies