Skip to content

Config overrides site doc #642

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

Merged
merged 11 commits into from
Dec 14, 2018
Merged

Config overrides site doc #642

merged 11 commits into from
Dec 14, 2018

Conversation

tbarnes-us
Copy link

This is the initial draft of the config overrides documentation.

@markxnelson
Copy link
Member

@tbarnes-us I will go ahead and merge this, but please have a look at the user-guide.md and let me know where you think this belongs in the table of contents, so I can add a link. thanks

@markxnelson markxnelson merged commit 6ca48f5 into develop Dec 14, 2018
Copy link
Member

@alai8 alai8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Is the Domain CR field configOverride or configOverrides?

@moreaut
Copy link
Contributor

moreaut commented Dec 14, 2018

It should be 'configOverrides'

@tbarnes-us
Copy link
Author

@moreaut I keep messing up with that one - I find the name to be confusing, since it refers to a singleton. Thus the original idea of naming it 'configOverrideConfigMap' to make it extremely clear it's a config map, and to make the relation to 'configOverrideSecrets' crystal clear too.

@tbarnes-us
Copy link
Author

But I guess this confusion isn't enough justification to make such a change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants