You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of #267, we're making sure Maestro/ES doesn't assign "random" mappings for indices not found.
Those mappings should be made available for customisation per projects' needs, which will be set on "runtime" not just at "build" time.
Note: Considering Maestro generally runs within a container, the injection of these values could be handled through Helm configmaps and/or Docker volumes.
The text was updated successfully, but these errors were encountered:
As part of #267, we're making sure Maestro/ES doesn't assign "random" mappings for indices not found.
Those mappings should be made available for customisation per projects' needs, which will be set on "runtime" not just at "build" time.
Note: Considering Maestro generally runs within a container, the injection of these values could be handled through Helm
configmaps
and/or Dockervolumes
.The text was updated successfully, but these errors were encountered: