creating new user.toml does not cause an already running service to reload impacted templates #7678
Labels
Focus:Supervisor
Related to the Habitat Supervisor (core/hab-sup) component
Type: Bug
Issues that describe broken functionality
Comments
christophermaier
added
Focus:Supervisor
|
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. |
|
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. |
1 similar comment
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you run a service and then add a new
user.tomlfile where the service did not previously use auser.toml, the running service will not react to the new toml values. However changing the values of auser.tomlthat was present when the service was started will cause a template rerender.The text was updated successfully, but these errors were encountered: