-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Config refactor burn down #3492
Labels
theme/internal-cleanup
Used to identify tech debt, testing improvements, code refactoring, and non-impactful optimization
type/docs
Documentation needs to be created/updated/clarified
Milestone
Comments
Caught this panic while running unit tests:
|
I'll have a look at this one. The |
Didn't push |
Monkey patches:
|
slackpad
added
type/docs
Documentation needs to be created/updated/clarified
theme/internal-cleanup
Used to identify tech debt, testing improvements, code refactoring, and non-impactful optimization
labels
Oct 5, 2017
Leaving the docs just on the website has been working for now (even without x-ref links). Let's keep this way for now and close this out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
theme/internal-cleanup
Used to identify tech debt, testing improvements, code refactoring, and non-impactful optimization
type/docs
Documentation needs to be created/updated/clarified
This captures some small cleanups from #3480, now that it has been merged:
ui
config was renamed toenable_ui
, breaking existing configs - Renamesenable_ui
toui
to keep compatibility with existing configs. #3496..json
or.hcl
extension for all config files - Enforce json or hcl extension to Consul config files, updated unit tests #3494.Token
field of checks and services in /v1/agent/self output (sanitize routine should be made recursive, it's only hitting the top level) - Recursive sanitize #3505.hashicorp/go-sockaddr
andhashicorp/hcl
andmitchellh/mapstructure
.Decide where to put the documentation that was part ofagent/config.Config
. We can either restore it to theConfig
struct, add it to theRuntimeConfig
or omit it from code altogether and put it in the public documentation. Plan is to use website as canonical and place link to that in the code. Internal-only configs will be documented in the code, but for all public stuff the website is the source of truth.The text was updated successfully, but these errors were encountered: