Skip to content

[Suggestion]: Add function to push/pull env variables #21

Open
@saltytostitos

Description

@saltytostitos

I'm a solo dev, so managing environment variables is annoying. I could use a service, but I like the idea of Nuxt HUB helping here.

Suggestion:
Add a CLI function nuxthub variables pull to download a fresh .env file of the variables stored on CF.
Additionally nuxthub variables push to upload variables (also reducing browser trips).

I often, lazily, use wrangler to download a config on a fresh pull: wrangler pages download config project_name and move my variables to some ignored filed. But, would be nice to save a few steps!

Notes
I know CF has a get at .../pages/projects/name that allows you to pull all the pages config data, and a patch at .../pages/projects/name to push data back.

I'm assuming you're using these calls inside the nuxthub backend.

How feasible is this? Also, potentially/alternatively, nuxthub could have a premium vault feature to make these things easier. Maybe?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions