Chore add command to manage runtime configuration #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fraxken
reviewed
Apr 28, 2022
|
Right now i would say that the default configuration we want is |
…imal" instead "complete"
…mmand-to-manage-runtime-configuration
|
@allcontributors please add @Kawacrepe for code, bug |
|
I've put up a pull request to add @Kawacrepe! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #100
This PR aims to add the foundations for managing .nodesecurerc through the CLI.
What is the default .nodesecurec configuration we want to create with
nsecure config create?Atm I use the 'complete'
There is some improvements to do here:
I'll create the different issues when this PR will be merged