Replies: 12 comments 3 replies
-
we have 15 secrets.... in 4 environments... as a manual job via a suboptimal web interface (you know what I mean) |
Beta Was this translation helpful? Give feedback.
-
We have around 50 secrets and variables, and it is tedious to manually enter them. What am I doing wrong? 😢 It would be interesting to have a feature that allows us to "clone" the environment without the values (part of the work would already be done, and the rest would depend on each individual). In the meantime, I suppose using a script with this API can be a good alternative to automate the creation of secrets. https://docs.github.com/en/rest/quickstart?apiVersion=2022-11-28 |
Beta Was this translation helpful? Give feedback.
-
we too have 25+ secrets and it is painful tasks to recreate them manually with different environment like dev,test,preprod and prod. Though it is one time activity, but cloning environment feature will really be a big help. |
Beta Was this translation helpful? Give feedback.
-
About to take on the task of replicating several environments and it is daunting. Being able to replicate var/secret names in an env template would be really valuable. |
Beta Was this translation helpful? Give feedback.
-
this is an ongoing issue with secure environments. safety and security requirements versus automation. |
Beta Was this translation helpful? Give feedback.
-
Hi! We have the same problem with Environments creating - 6 env with a huge amount of secrets/variables |
Beta Was this translation helpful? Give feedback.
-
Same Problem With Env's creating. If we can clone them it will be very helpful. |
Beta Was this translation helpful? Give feedback.
-
yes, this is a necessary feature |
Beta Was this translation helpful? Give feedback.
-
Copy option in UI would be great. As a workaround I try to manage my env secrets and variables using Terraform. There is a github provider available and you can create some reusable module that can be parametrized. Then you reuse this module multiple times with different environment parameters. The |
Beta Was this translation helpful? Give feedback.
-
Same problem, ability to rename and/or copy environments would be very useful! |
Beta Was this translation helpful? Give feedback.
-
i like how other modern hosting providers will let you copy and paste a .env file's contents into a box and it generates the secrets config for you. |
Beta Was this translation helpful? Give feedback.
-
We are the same but mostly creating almost the same environment on all our repos we only 1-2 different fields different for the same environment on the different repos. Either having org wide environment you could inherit into a repo environment and override or being able to duplicate or export/import an environment would be great. Even if it excluded secrets or needed extra auth and restrictions to duplicate the secrets over |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
It would be really handy if we could copy a GitHub Repo 'environment' to make a new environment.
ref: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment
For example, you'd setup your Development GHA environment, debug it, then copy to "production' and make whatever changes are needed to anything but Secrets (recreating those as necessary). It would save a lot of typing, and occasional hard to track bugs like an environment variable having a misspelling.
For security reasons, maybe copying the environmental secrets wouldn't be a good thing, but I just had to retype 3 sets of 8 environment variables ... whew.
Beta Was this translation helpful? Give feedback.
All reactions