Skip to content
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.

Sign up for GitHub

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

Jump to bottom

API server: "write once, read many" functionality for settings #1663

Open
zmrow opened this issue Jul 21, 2021 · 2 comments
Open

API server: "write once, read many" functionality for settings #1663

zmrow opened this issue Jul 21, 2021 · 2 comments
Labels
area/core Issues core to the OS (variant independent) status/icebox Things we think would be nice but are not prioritized type/enhancement New feature or request

Comments

@zmrow
Copy link
Contributor

zmrow commented Jul 21, 2021

What I'd like:
I'd like a setting type that can only be set once, but read freely.

This would come in handy for things like settings.network.hostname, where we wouldn't want users to be able to change it after it is set, which can cause issues with kubelet.

Related to #1608
@zmrow zmrow mentioned this issue Jul 21, 2021
Merged
@zmrow zmrow added area/core Issues core to the OS (variant independent) priority/p2 type/enhancement New feature or request labels Jul 22, 2021
@webern
Copy link
Contributor

webern commented Jul 22, 2021

We should consider also that a hostname may be writeable without consequence in some variants but in other variants we might want it to be 'write-once'.

@jhaynes jhaynes added this to the backlog milestone Aug 3, 2021
@Vaishvenk Vaishvenk modified the milestones: backlog, techdebt Sep 8, 2021
@stmcginnis stmcginnis added status/needs-triage Pending triage or re-evaluation and removed priority/p2 labels Dec 1, 2022
@stmcginnis stmcginnis removed this from the techdebt milestone Feb 23, 2023
@stmcginnis
Copy link
Contributor

@cbgbt another fyi for settings...

@stmcginnis stmcginnis added status/icebox Things we think would be nice but are not prioritized and removed status/needs-triage Pending triage or re-evaluation labels Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/core Issues core to the OS (variant independent) status/icebox Things we think would be nice but are not prioritized type/enhancement New feature or request
Projects
Bottlerocket Engineering Roadmap
Status: No status
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jhaynes @zmrow @stmcginnis @webern @Vaishvenk