run provider command as a sub command to init #184
Merged
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.
Summary and Scope
init
command works ok for one provider, but when adding more, clashes can occur if two providers set the same flags. This change makes a new provider command for each provider, and merges CANI's flags with it. This results in each provider having CANI's flags and their own, without clashing with another provider. To accomplish this, the command name is the same as the provider via theSlug()
method, and then when an argument tosession init
is a valid provider, it executes the providers init commandif cmd.Name() == "init"
s toif cmd.Parent().Name() == "init"
sinceinit
calls subcommandsRisks and Mitigations