Describe the bug
I set the client config to a different port, but Migrations still run on the default port. I am running two different versions of ES at the same time.
I am not sure if this is a bug, or I have some config that is wrong. But I just can't get migrations to to run on my port 28201 instance.
I am using version 2.0.1.
I would like to upgrade to 3.3 but finding it difficult to have a combination that works with elastic-scout-driver-plus.
ELASTIC_MIGRATIONS_CONNECTION='main'
# Configuration for ES version 8
ELASTICSEARCH_8_CONNECTION=default
ELASTICSEARCH_8_CLUSTER_MAP=localhost:28201
ELASTICSEARCH_8_HOST=localhost:28201
ELASTICSEARCH_8_SCHEME=http
ELASTICSEARCH_8_USER=
ELASTICSEARCH_8_PASS=
Current behavior
The index is created in the ES on port 9200.
Expected behavior
The index is created in the ES on port 28201.
It looks like a lot of changes for multiple connections was made in v3. I am not able to upgrade because of another conflict. For now I will handle migrations differently.
Describe the bug I set the client config to a different port, but Migrations still run on the default port. I am running two different versions of ES at the same time.
I am not sure if this is a bug, or I have some config that is wrong. But I just can't get migrations to to run on my port 28201 instance.
I am using version 2.0.1.
I would like to upgrade to 3.3 but finding it difficult to have a combination that works with elastic-scout-driver-plus.
When I try migrations ^3.3, I end up with dependency conflicts I can't seem to resolve.
Thanks for any assistance you can provide.
To Reproduce Set client config to:
.env:
Current behavior The index is created in the ES on port 9200.
Expected behavior The index is created in the ES on port 28201.