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

Elasticsearch URL & Host Mess #307

Merged
merged 6 commits into from
Aug 20, 2021
Merged

Elasticsearch URL & Host Mess #307

merged 6 commits into from
Aug 20, 2021

Conversation

Schnitzel
Copy link
Contributor

Our values for elasticsearch is a mess, we have multiple ways to define the same thing.
This change now just uses elasticsearchURL like we already have kibanaURL and other xxxURL
Turns out that all services in lagoon core can handle full URLs with Scheme and Ports (like they should), so it's probably the best to do it this way.
As soon as uselagoon/lagoon#2786 is merged we can also remove ELASTICSEARCH_HOST but until then I would leave it in for BC

basically both `ELASTICSEARCH_HOST` and `ELASTICSEARCH_URL` should use full URLs (with schemes and ports) or the connection might not work
@tobybellwood
Copy link
Member

Merged into #318 with the release that removes ELASTICSEARCH_HOST from lagoon-core.

Note that logs-concentrator still uses ELASTICSEARCH_HOST in this chart (and presumably other ones upstream)

@Schnitzel Schnitzel merged commit 9f1bc66 into main Aug 20, 2021
@Schnitzel Schnitzel deleted the elasticsearch-url-mess branch August 20, 2021 11:31
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.

None yet

2 participants