-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
⚠️ Inject filesystem from CLI instead of creating several per command #2080
Conversation
f31866d
to
1761213
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a small change which I agree with 🥇
However, as it is a breaking change would be nice to get a second thought as well.
Could you please check if another person can review and is ok with either?
Signed-off-by: Adrian Orive <[email protected]>
5bbf9ad
to
a2cc78c
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Adirio, camilamacedo86, estroz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
A new filesystem abstraction is being created in multiple places. This PRs creates a single filesystem abstraction in the CLI, and passes/injects it to any machinery that requires it.
Technically speaking this is a brekaing change, because it modifies the
Subcommand
interface inpkg/plugin/interfaces.go
. This, and the corresponding signature update for the plugins, is the only breaking change in this PR. It is required to expose both the scaffolding machinery (#2036) and the config file machinery (#2056).