Provide option to edit the Git repository settings, an existing stack

[bitwon]

Is your feature request related to a problem? Please describe.
If you use Git for a stack and something like the repository URL changes or the branch, you're not able to update the Git related settings. You have to create a new stack instead of modifying the existing one.

Describe the solution you'd like
Provide an option to modify a stack attached to Git.

Describe alternatives you've considered
Not known.

Additional context
Portainer KB article.

[cf-sewe]

I was actually surprised, that editing the branch is no longer possible in Portainer 2.16.
Its quite useful to adjust the branch for testing purposes.

Update: Just noticed that also Environment variables can no longer be changed, but this is quite necessary for our workflow.

[cf-sewe]

This is meanwhile resolved (checked in portainer 2.21), editing Repository Reference (Branch) & Environment work.
Editing the Repository URL is still not possible.

[AlthaTechnology]

This would be helpful for us as well. The recent update of Portainer just broke some of our paths. I believe we were putting them in wrong, but it did work and now doesn't. Being able to update this on the stack after it's deployed would be helpful.

Having the / in front now doesn't work, whereas I think we needed it in the previous version.

[tamarahenson]

@AlthaTechnology

Thank you for the additional information. Do you remember what version that you could previously use the /

Thanks!

[AlthaTechnology]

@tamarahenson Sure, 2.16.2 it was working. The previous release. I also do have some stacks we deployed without it in that version as well, so the path was put in both ways previously and working.

[ohmantics]

Just hit this. Scrypted moved where docker-compose.yml is in the repo and it broke the stack.

[Nick-Portainer]

Thanks for bumping this, I am raising it internally and will reply here after the discussion to give an update.

internal: PCT-214

[ThaDaVos]

Any update on this? I am about to move my gitserver to it's own domain - instead of being port based - but I don't want to re-create 19+ stacks....

[Nick-Portainer]

Hey @ThaDaVos, This is still with the Product team under review

[ThaDaVos]

So, few months later, still no update @Nick-Portainer ?

[Nick-Portainer]

Our product team have agreed to look into this, but I can not provide an ETA at this time. I will update here with any progress

[astronaute77]

Bumping this again, I too need to migrate a huge repository to another one and am stuck.
Thank you

[mukeshwani]

Same here. Has anyone found a backend way? might be a setting stored in DB?

[chriszuercher]

I was surprised this is not working. I had to fork a Github Repo with the docker-compose, but now cannot change the GIT remote. So this is quite essential.

Is there any update on this topic?

[timwedde]

Also found this to be a surprising limitation, one would think that this is possible at first glance, especially since the documentation makes no note of the fact that it doesn't work for particular types of stacks, either.

[phillf]

I have probably 30 total containers I need to update Git remotes for. I am pretty sure there are are others in far worse situations than I.

Why is this not a possibility in current state Portainer?

[srad]

Do I have to recreate the stack right now when I want to change the Git remote URL?

[phillf]

Annoyingly, yes.