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

Honor tlsSecretName from ES application config #142

Merged
merged 1 commit into from
Jul 4, 2023

Conversation

csibbitt
Copy link
Contributor

Currently we set a default tls_secret_name in the role, but have no way of supplying an override in the SmartGateway object. Adding it to the CRD seemed out of place because it's really only used for Elasticsearch, so I added it to the "freeform application config" that STO constructs for Elasticsearch[1]. This change allows the new config item to be honored, falling back to the existing default if it's not there. It feels a bit strange because that config is otherwise passed directly into sg-core, and this is only used by the operator, but this still seemed like the only logical place to add it.

[1] https://github.com/infrawatch/service-telemetry-operator/pull/439/files#diff-b661f3e2be8a3856711ae0ed99adda16e30a66a972ec5dc5118f57bfbf3ffe2dR22

@csibbitt csibbitt merged commit b028753 into master Jul 4, 2023
@csibbitt csibbitt deleted the csibbitt_STF-1385_external_es branch July 4, 2023 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants