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.

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

Clarify usage of hab config apply #3977

Open
christophermaier opened this issue Nov 1, 2017 · 4 comments
Open

Clarify usage of hab config apply #3977

christophermaier opened this issue Nov 1, 2017 · 4 comments
Labels
Documentation Flags an issue / PR for attention by the technical documentation team Stale

Comments

@christophermaier
Copy link
Contributor

christophermaier commented Nov 1, 2017

The documentation example for hab config apply at https://www.habitat.sh/docs/using-habitat/#config-updates can be misleading. By using a single key-value pair (and by the fact that the command is called apply), it can lead users to think that the Supervisor will "remember" the current configuration and just add the new value on top of it, which is distinctly not the case.

Having a more complete example, along with a more detailed explanation of the layering of configuration that happens (e.g., default.toml as base, with environment, user.toml, and hab config applyd config layered on top of that) would help clarify how things are actually behaving.

@rsertelon
Copy link
Contributor

This is linked to #1059 I think

@tduffield
Copy link
Contributor

Just to add onto this, documenting the /hab/user directory to some degree would be nice as well. I noticed a deprecation message saying I needed to move my user.toml to /hab/user/<svc>/config and didn't really have any guidance as to what /hab/user even was.

@stale
Copy link

stale bot commented Apr 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

@stale stale bot added the Stale label Apr 2, 2020
@christophermaier christophermaier added Documentation Flags an issue / PR for attention by the technical documentation team and removed A-documentation labels Aug 18, 2020
@stale stale bot removed the Stale label Aug 18, 2020
@stale
Copy link

stale bot commented Jul 31, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

@stale stale bot added the Stale label Jul 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Flags an issue / PR for attention by the technical documentation team Stale
Projects
None yet
Development

No branches or pull requests

5 participants