Open ycombinator opened 1 year ago
Haven't we already made the breaking change by ignoring the argument? Anyone relying on this has already had their use case broken.
@cmacknz No because you can still provide the --path.install
to the Elastic Agent and it won't error. If we remove it then it would be breaking as the Elastic Agent would fail to start. We also didn't break any use-case because we no-longer extract to any directory so its not needed.
What about we at least edit the description of the flag to state it is deprecated and ignored?
On v8.11.1
(the latest release at the time of writting) we still have:
--path.install string Install path contains binaries Agent extracts
We could edit the message to something like "DEPRECATED, setting this flag has no effect". Or even add the version: "DEPRECATED, setting this flag has no effect since v8.6.0".
That way we do not break anything, keep the current behaviour and better inform the users about the current behaviour.
@belimawr good idea, go ahead and a make PR for it.
As per the conversation starting from https://github.com/elastic/ingest-dev/issues/1609#issuecomment-1503384831, the
--path.install
option is no longer being used by Elastic Agent. We should remove it but, since that would be a breaking change, we should do this in 9.0.Copying relevant bits of the conversation here for easy reference:
@blakerouse said:
@ycombinator asked:
@jlind23 confirmed: