Closed FlorentLvr closed 5 months ago
@Dr0p42, sounds great!
This issue needs https://github.com/jupyter-naas/naas-python/issues/33 to be completed first
This issue is also blocked by this one: https://github.com/jupyter-naas/naas-python/issues/32
Addition @l-loic , can you add some logic to:
if /home/ftp/.naas/secrets.backup.json does not exists: copy /home/ftp/.naas/secrets.json /home/ftp/.naas/secrets.backup.json
This will ensure that we have a backup just in case.
We need to make use of the new naas-python.secret SDK. The way we handle secrets should be as follow now:
As a user when I want to get a secret value:
As a user when I list secrets:
As a user when I want to create a secret:
As a user when I want to delete a secret:
Doing so, secrets should move from local to api smoothly.
This should allow us to do a drop in replacement of the way we store secret.