-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix: AdminService, config & secret CLI refactor, --op=VAULT
deprecated
#1565
Conversation
10b4956
to
678853f
Compare
…ers, adds `--opvault=VAULT` controller flag (#1604) This change is a precursor to #1565. It removes the notion of `MutableProviders` and requires a provider be specified when calling mutable functions in the manager. It also allows a 1Password vault to be set at the controller & main.go levels by using `--opvault=VAULT`. To operate on 1P secrets via CLI, continue to use `ftl secret ... --op=VAULT`, but this should eventually change to a bool flag.
c5343d0
to
2ad12ee
Compare
--op=VAULT
deprecated
2ad12ee
to
95706f6
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.
LGTM
package controller | ||
|
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.
To follow the pattern we have now, maybe this should go in an admin
package here in the controller?
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.
Also, we should add some tests for this new admin
:)
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.
Addressing in a separate PR :)
Should this go in? |
95706f6
to
55441b0
Compare
Fixes #1473 by providing an
AdminService
and refactoringcmd_config.go
andcmd_secret.go
to use that service. The following CLI changes are included that may break existing clients:ftl config
andftl secret
now require a running controllerftl secret set <ref> --op=VAULT
is no longer supportedftl-controller
andftl dev
accept a 1Password vault using--opvault=VAULT
ftl secret set <ref> --op
is supported, whereop
is a bool flag that requires the controller to have an--opvault