Remove dependency on local storage about cloudmos HOT 3 OPEN

Experienced this issue as well after clearing my browser cache. Lost significant samples of my previous sdl. Luckily I have some useful templates I collected backup elsewhere. In my case, this loss of cert, fav, and sdl happens for both Cloudmos and Console. I have been testing the two for more than a month now. Console is certainly getting better fast these days. Hope the migration will goes smooth. Console is now my go to for new deployments. So maybe implementation on Console should be prioritized when possible.

About the options. Option 1 will be great, so one can download everything right away. If user want to back it up again elsewhere and sync things to be more organized that's up to them. For Option 2, The direct cloud storage solution perhaps is for a bit later. When it is later considered perhaps data from each deployment can be sync to some decentralized cloud associated with the keplr wallet address used for deployment.

from cloudmos.

Thanks for the comment. Yea, we're getting to this quite soon.

When it is later considered perhaps data from each deployment can be sync to some decentralized cloud associated with the keplr wallet address used for deployment.

There are some considerations against this. Like data can contain sensitive things. E.g. private registries creds. So we're still thinking how to approach this in the long run

from cloudmos.

A PR is available with a temporary solution for export/import functions. To transition towards a more robust version (which would still be incomplete), I'd propose the following steps:

• Introduce a new tab in the deployment for adding secrets.
• Store secrets within a cookie.
• Enable referencing of secrets in templates.
• This allows for secure storage of SDLs on the backend without secrets, leaving responsibility to a user.
• In the UI, secrets will be displayed as asterisks to indicate their necessity for the template while maintaining write-only access.
• Secrets export/import functionality will be supported, accommodating formats like dot files and JSON.
• Once secret management is refined, we can relocate storage, with the UI adjustments already in place.

Following the GitHub Actions model, the secret management would involve:

1. A two-field form: a name text input and a secret multiline textarea.
2. Secrets can be accessed using the syntax: ${{ secrets.SECRET_NAME }}.

Let's discuss this and if this works I can continue with the implementation.

from cloudmos.