Environment Merging Doesn't Work
I created a new project and accidentally started an environment fork / merge thing. Now my staging has more containers than production and trying to do the "Review 79 Changes", doesn't work. After I click the first change, no other clicks work and I'm stuck in a loop of not being able to approve or reject anything.
22 Replies
Project ID:
9c41e196-5568-4e75-85e0-0aa8aac798409c41e196-5568-4e75-85e0-0aa8aac79840
I can't get rid of this:
The "keep it" and "ship it" buttons only work for the first item in the list and then don't.
I'm not able to complete the flow.
And so not really able to deploy to production. I'm worried that re-creating services and such in my production environment will create a weird situation and break things.
@Brody @Angelo pls help
#🛂｜readme #5
no not ping conductors, and especially do not ping the team
sorry, didnt see that
Did you delete my bug report in #🚅｜priority-boarding ? The description of the channel says "Only use this channel for reporting bugs in beta features."
I was reporting a bug in a beta feature. The docs clearly state that it is a beta feature.
Thread has been flagged to Railway team by @Ray.
This seems related, but I cannot update values for new services in the production environment. The app doesn't provide more information than a "failed to update" toast.
So I don't think I can replicate the staging environment in production as a work around unfortunately.
Hey Connor! Just came back from PTO, I am going to work with you to see the issue that might be at hand.
I am going to DM you a link so you can book time with me and I can directly debug it on a call or I can try to do it async (I have 2 meetings left in the day)
Thank you!
Update: Selecting through most of the items works now! However, there is still a dead screen with the random 11 unresolved items and no ability to continue
Might be somehow related to the weird starting state from this project
cc @gimenete for visibility
I see. Sorry about that. We are filtering out some values that were redundant but the logic for moving to the next screen is still not correct. I hope to have a fix for this tomorrow.
I appreciate that! I also understand that I am using a beta feature and that by definition it won't be perfect 🙂
Thanks! I'll keep you updated once the fix is deployed.
Thank you!
Hey. I've deployed some changes and the UI problems should be fixed. You will still see a big list of changes, but you should be able to merge keep/discard them in the UI.
Additionally I'm working on a change to prevent so many changes to appear in the merge panel in the future. In your case this probably happened because you used the raw env variables editor. The editor recreates all the variables internally and that makes the diff view to think that all variables have changed. With the improvement I'm working on, that will be no longer the case.
Let me know if you still find issues using the merge functionality. Thanks!
It worked! Thank you! A small nit I have: when merging the variables that are essentially "shared variables" from a railway-managed DB service (like Redis), the "value" that it shows in the merge UI is something to the effect of the UUID of the service, but once it's merged into the other environment, it shows it as
${{Redis.REDIS_URL}} or whatever. If the merge editor showed the ${{Redis.REDIS_URL}} value instead of the UUID one, I would have higher confidence that it was doing what I wanted (I kinda just guessed and got lucky this time). Happy to rephrase if that doesnt make sense.
But yeah I probably either used the raw editor or just had way too many changes that I ignored or something to that effect. Regardless, thanks again!
Going to mark this as solved.!resolve
@Brody has marked this thread as resolved.
Cool that it worked! I'll look into the shared variables thing. Thanks for sharing it!