You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, NuxtHub does not automatically suggest encrypting sensitive fields like NUXT_UI_PRO_LICENSE. While some contextual information is added for certain keys, it would be beneficial if the environment variable manager could detect potentially sensitive fields and prompt users to store them as secrets rather than plain variables.
Additionally, when defining secrets in NuxtHub, they are only sent to Cloudflare but not to GitHub. If it’s truly impossible to automatically sync secrets with GitHub, there should at least be a warning when using GitHub Actions, reminding users to manually update secrets if they modify one in NuxtHub.
The text was updated successfully, but these errors were encountered:
Currently, NuxtHub does not automatically suggest encrypting sensitive fields like NUXT_UI_PRO_LICENSE. While some contextual information is added for certain keys, it would be beneficial if the environment variable manager could detect potentially sensitive fields and prompt users to store them as secrets rather than plain variables.
Additionally, when defining secrets in NuxtHub, they are only sent to Cloudflare but not to GitHub. If it’s truly impossible to automatically sync secrets with GitHub, there should at least be a warning when using GitHub Actions, reminding users to manually update secrets if they modify one in NuxtHub.
The text was updated successfully, but these errors were encountered: