# Custom pugin version

**URL:** <https://discuss.elastic.co/t/custom-pugin-version/221669>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [March 2, 2020, 11:51am UTC](https://discuss.elastic.co/t/custom-pugin-version/221669 "2020-03-02T11:51:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vincent.arnaud90](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@vincent.arnaud90](https://discuss.elastic.co/u/vincent.arnaud90)\
**Post date:** [March 2, 2020, 11:51am UTC](https://discuss.elastic.co/t/custom-pugin-version/221669/1 "2020-03-02T11:51:45Z")

</div>

Hello, I have a custom plugin and I'd like to know if it's possible to make the version dynamique directly in rally.ini's `[distributions]` section ? The plugin does not follow elasticsearch's version numbers as there are multiple plugin versions for a single elastic version, so placeholder `{{VERSION}}` doesn't work in this case.  
I'm aware that I can build it from sources with specific git revision using `--revision` flag but I'd like to avoid that as it's already build and published somewhere.

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [March 3, 2020, 3:59pm UTC](https://discuss.elastic.co/t/custom-pugin-version/221669/2 "2020-03-03T15:59:21Z")

</div>

Hi,

I am not sure I understood everything correctly based on your description so please tell me if I got it wrong. 🙂 You should be able to override the plugin download URL in `~/.rally/rally.ini` as specified in the [docs](https://esrally.readthedocs.io/en/stable/elasticsearch_plugins.html):

```auto
plugin.myplugin.release.url=https://example.org/myplugin/releases/myplugin-version-1.2.3.zip

```

i.e. you can hardcode the URL; there is no need to use `{{VERSION}}`.

you can also probably "fake" your custom variations by having multiple plugins in there (not tested):

```auto
plugin.myplugin-1.2.3.release.url=https://example.org/myplugin/releases/myplugin-version-1.2.3.zip
plugin.myplugin-2.3.4.release.url=https://example.org/myplugin/releases/myplugin-version-2.3.4.zip

```

You should be able to refer to your plugin then on the command line with `--elasticsearch-plugins=myplugin-2.3.4`. It might be a bit inconvenient this way (depending on how many custom versions you have) but I hope that helps.

Daniel

---

<div class="post-metadata">

**Author:** ![vincent.arnaud90](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@vincent.arnaud90](https://discuss.elastic.co/u/vincent.arnaud90)\
**Post date:** [March 4, 2020, 9:34am UTC](https://discuss.elastic.co/t/custom-pugin-version/221669/3 "2020-03-04T09:34:52Z")

</div>

Hello, thanks for the reply.  
I didn't think about your variation but it's not really convenient in my case as I have decades of version and I'll need to keep `rally.ini` up to date when a new release is done.  
I gave it some thoughts and finally came to the conclusion that the best compromise is using `--revision` flag rather asking for a new feature in github that will not be so usefull.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 1, 2020, 9:34am UTC](https://discuss.elastic.co/t/custom-pugin-version/221669/4 "2020-04-01T09:34:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.