I think one of the reasons is that a defined namespace allows Livebook to detect “environment variables” that Livebook is supposed to manage and give them special treatment.

Here’s a quick GIF video showing that difference:

https://media.cleanshot.cloud/media/43831/WaBMHyltLpa5qhcC7JEAGTUgS4BAO83zkRScC3ZY.gif?Expires=1679708197&Signature=nIZ4VR87LGR5Jwh28eMFrliKZrH4VFtDgL2RsLxXYM5HYzZ0ed9FjGJ8gQqtZas1y82uDm1k52O-TaLdiHB4OE7xUUeGP9FiLQWOt19QXRW8BEIdvPLm1NK3hecAzKOr0YxHQjeIE5znKd-uST-delo~RsSZh8FF5O5nfFZ-cWF--lqFBETfwfxwhhsua9JwMM4w04QbO2oUaWeSJ1bU2vYg1MDWVkEyofAW3-oM0h4EFE2sT1vClOY9iJfqmd2XGj5yBu1IAu0MtnY74n8UWXFYkvOR~CjSTy4DY5GFe0W965feeKyrY2HRejuD7sLIoqWLIo32murttmnjt6LEFQ__&Key-Pair-Id=K269JMAT9ZF4GZ

—skip—

I see no reason other than well intended namespacing…with confusion as result.

If that’s all there is to it, a simple helper text in the config modal would clarify.

This secret can be fetched with System.fetch_env!(“LB_SOME”)

@dmitriid maybe open issue marked as “usability issue”?

The issue got fixed immediately

I didn’t think it warranted an issue, but I might just do that the next time I run into this