-
Notifications
You must be signed in to change notification settings - Fork 18
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
lndinit: add ability to write to k8s configmap #38
Conversation
a9c7110
to
60df4b7
Compare
ObjectTypeConfigMap k8sObjectType = "ConfigMap" | ||
) | ||
|
||
type k8sObjectOptions struct { |
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.
If the rename of the CLI flag to the more general --k8s.name
is not preferred, we could just make a separate k8sConfigmapOptions
struct.
60df4b7
to
10064d3
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.
Thanks for the PR!
Very useful new function.
Main comment is about not breaking existing users by renaming flags. So we'd rather have some duplicated code.
I'll do a full review with manual tests once the diff is updated.
ba436e9
to
d23278b
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.
utACK, LGTM 🎉
We'll use this to write connection relateed information for consumption by payment service proxy.
d23278b
to
0238e58
Compare
This PR equips lndinit with the ability to write arbitrary key/value data to a Kubernetes Configmap object.
base64
encoded.