-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RNV does not create encrypt destination folder #930
Comments
on 1.0.0-canary.4 rnv doesn't show error in the end of the logs that .secrets can't be found
|
In canary.8 noticed also that rnv doesn't create decrypt destination folder and contents, if user runs
|
Same issue in 1.0.0-rc.3 as in main description, secrets folder isn't created, test on template-starter |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When encrypting data on new project, rnv asks to define where encrypted data will be stored (default is ./secrets) but renative doesn’t create that folder and you need to create it manually to make encrypt work
To Reproduce
npx rnv crypto encrypt
Expected behavior
RNV creates destination folder
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: