100 environment variables for GitHub Actions is not enough #63159
Replies: 4 comments
-
Bump. Same issue on our end |
Beta Was this translation helpful? Give feedback.
-
GitHub Support has told us that 100 is enough for most of their customers and they will not be increasing it. We have had to move all of our Secrets and Variables out of GitHub and to AWS Parameter Store to avoid the limitations. |
Beta Was this translation helpful? Give feedback.
-
Same problem on our end! |
Beta Was this translation helpful? Give feedback.
-
It is pretty scary and disheartening that GitHub does not care about their customers and does not address issues for years. Those arbitrary limits are probably some variable somewhere set by someone who thinks everyone works same way. It is pretty hard to believe that increasing this limit will affect GitHub in any significant way. Not to mention that someone asked support and response was: |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
We have a monorepo set up for our projects, which works very well for us. However, we have multiple containerized services deploying from it. At this time, we have easily hit the 100 variables per environment limit and would like it to be increased to 500 if possible.
Thanks,
Gregg Jensen
Beta Was this translation helpful? Give feedback.
All reactions