Yeah I’ve read through that thread, thanks for sharing it. I didn’t find where a solution to my problem is presented. Maybe you can be more specific if you feel there is a solution there.
To put my problem more simply, the sum total of all Netlify UI env vars exceeds 4kb. >1kb needed in the react app, >1kb needed in ALL Netlify Lambda Functions, and >3kb is only needed in a SINGLE Netlify function and not needed on the front end React app at all nor any of the rest of the sites functions.
As it currently behaves, the deploy of the Netlify Functions includes ALL env vars (without magic prefixes for front end). This behavior of including all env vars in each function deploy causes the Lambda deploys to fail.
My goal is to be able to use the Netlify UI to manage all of the env vars in a single place outside of the repo. I could use env files and develop a webpack customization and a host of other solutions some I believe are outlined in the guide you linked to.
In the spirit of what makes Netlify the simplistic gem that it is, I’d like to be able to use the Netlify UI to manage all env vars. Using the Netlify UI has benefits over dealing with .env files that are git ignored and need to be shared among team members manually.
Are there any solutions to this issue that keep the Netlify UI as the single source of truth for all env vars for a site but allow us to manage them with more precision when the total gets beyond 4kb in size?
Are there any plans to make configurable which env vars from the Netlify UI are included during a functions deployment to AWS?
Are namespaces for Netlify UI env vars being considered? I think this or a configuration in the Netlify.toml to choose which env vars to include in a functions deployment would work too.
Are there any ways to gain access to this process to control the deployment steps? I looked at build plugins but they appear too early and we would not be able to control which env vars are included in the deployment of the Lambda to AWS. Correct me if I’m wrong please.
Thanks in advance and I want to say that I really like Netlify. Just trying to find a way to use it for how awesome it is without having to resort to workarounds etc. When I have to start doing workarounds and custom scripts and external env file management etc, the platform loses some of its benefit of simplicity and ease of use and creates a risk in presenting a simple facade but in actuality has hidden complexity that mirrors what we might see with a home grown CICD pipeline. In the latter, I’d rather have the pipeline owned 100% if it’s going to depart from what Netlify offers on the tin.