Ability to rename an environment

[greggbjensen]

Select Topic Area

Product Feedback

Body

We have many secrets set up in our environments, and unfortunately, the initial ones we created start with an uppercase letter. Now we have standardized on all lowercase letters to make common actions easier. However, we cannot rename an existing environment, clone it, or copy the secrets.

It would be great if we could rename an environment to fix this.

[christophercouch]

Hi @greggbjensen,

I see the challenge you're facing. Having the ability to rename an environment, especially when you're standardizing naming conventions, would indeed be a helpful feature. This would also simplify the process of managing secrets and environments without having to recreate everything from scratch.

I'd recommend submitting this as a feature request directly through the GitHub feedback form. This ensures the GitHub team can evaluate your suggestion.

Thanks for sharing your feedback!

[risoms]

@christophercouch Has there been any update to this? I can imagine there is a shared need of this across many users.

[amigos-sian]

hi @christophercouch , also keen for an update on renaming environments. Reason for this is that we have environments that we no longer needed, but you wouldn't want to delete them as the environments provide a record of past deployments which is important for audits etc. To further define the issue: "As a developer, given I have clicked on an environment, under Settings/Environments for a repo, I would to click on an option to rename an environment under the configuration settings".

[AnijaJacob]

+1 for this enhancement request.
Given the flexibility with GHA , we are using same as the single orchestrator for all deployments . Manuel migration to new environments with 40+ vars instead of a simple name change would be time consuming

[FinOCE]

+1 as well. I don't have as many vars and secrets but would still be a pain!