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
there's no support for secrets right now if you're trying to run from CI or similar you could save the JSON file (with your secret) as an env var and "echo" it into the environment before starting the migration phase. Something like
echo $MIGRONDI_CONF > migrondi.json
which is what I do on GitLab's CI, for example with my gcloud service keys
...
deploy:
stage: deployscript:
...
- echo $GCP_SERVICE_KEY_STAGING > gcloud-service-key.json # Google Cloud service accounts...
there are a couple of ways we can do this as well we can take them as cli arguments or try to read them from the environment
hey @brettrowberry I just recently switched to Argu and argu allows you to add an environment variable reader, so we could add it to the commands options or actually read it from the environment when trying to create a connection, let me know if you are interested in adding this or otherwise also let me know if I can close this issue
How should I manage a connection string with a secret?
The text was updated successfully, but these errors were encountered: