Joe Marty

@tianon That would be great! Although that buries it a little bit... I'm torn on this because, as much as I would love to believe that everyone knows to RTFM...

I believe this is supported as follows: ```yml ignore_missing: de: - 'admin.*' - 'admin_mailer.*' - 'teacher.*' - 'teacher_mailer.*' es: - 'admin.*' - 'admin_mailer.*' - 'teacher.*' - 'teacher_mailer.*' ... ``` And...

It looks like this has been added to the [guide](https://guide.elm-lang.org/types/type_aliases.html), but not the syntax docs. It does seem like an important part of the syntax to me... from a user...

I agree that this is a bug, not an enhancement. (But I guess maybe our definitions are different than Hashicorp's?) How are we supposed to import any existing infrastructure into...

One alternative solution to at least provide a sensible workaround would be to allow us to mark a variable in TF cloud as "disabled" so that we don't have to...

This is indeed confusing! The note in question was added in this PR: https://github.com/vercel/next.js/pull/20869, addressing this issue: https://github.com/vercel/next.js/issues/19420. I think perhaps it only applies to environment variables that begin with...

(@timneutkens maybe you could also provide input/confirmation here, having approved that PR?)

@eps1lon - So you're just looking for a note confirming that, something like "any variables in the runtime environment that don't appear in a .env file will be passed through...

@nick4fake - I was not trying to be dismissive, just trying to find a documentation update that might alleviate @eps1lon's confusion. It sounds like you have other questions/confusion about env-related...

@g-monroe I agree this is not really supported by the next framework going forward. We are currently still using the legacy [publicRuntimeConfig](https://nextjs.org/docs/pages/api-reference/next-config-js/runtime-configuration) for this purpose, which I hope continues to...