✨ Allow independent credentials for JSON RPC #518
Conversation
dtantsur
force-pushed
the
json-rpc-cred
branch
2 times, most recently
from
6fbe31a to
ed7f8c5
Compare
metal3-io-bot
added
the
size/M
|
/test metal3-ubuntu-e2e-integration-test-main |
metal3-io-bot
added
the
needs-rebase
dtantsur
force-pushed
the
json-rpc-cred
branch
from
e1f3075 to
a427363
Compare
metal3-io-bot
removed
the
needs-rebase
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
metal3-io-bot
added
the
lifecycle/stale
|
/remove-lifecycle stale |
metal3-io-bot
removed
the
lifecycle/stale
It's probably not a great idea to allow users to easily access JSON RPC, so a different set of credentials is useful. Also allow the secret to be mounted directly without the convoluted auth-config format (which is an ini file in reality). Deprecate the auth-config approach (JSON RPC is the last instance where it's used). Signed-off-by: Dmitry Tantsur <[email protected]>
dtantsur
force-pushed
the
json-rpc-cred
branch
from
a427363 to
7978e68
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
It's probably not a great idea to allow users to easily access JSON RPC,
so a different set of credentials is useful.
Also allow the secret to be mounted directly without the convoluted
auth-config format (which is an ini file in reality). Deprecate
the auth-config approach (JSON RPC is the last instance where it's
used).