Allow --version to overwrite addon version

[einschmidt]

Goal

Allow to set the build version for add-ons via the --version or -v parameter.

Use-case

Using the GitHub actions, I want to be able to use different actions for different purposes, and different results. For example:

• Action 1 builds and uploads the addon release docker files. This is currently possible
• Action 2 builds a dev/edge docker image that is using a specific tag/version which is different to the version of the stable addon, and which is not latest.

Change

1. Don't set a local version variable when building an addon
2. Read the version from config.json only when global version variable is empty (e.g. when not set, default)

desired example config

- name: Publish
  uses: home-assistant/builder@master
  with:
   args: |
    --all \
    --target /data \
    --version test \
    --docker-hub userspace-name

[homeassistant]

Hi @einschmidt,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[homeassistant]

Hi @einschmidt,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[ludeeus]

This does not enable --version for addons furthermore, this will break the build if --version is passed with --addon since version in the build_addon function will be blank.

[einschmidt]

Thanks for the review @ludeeus. I reviewed the variables and changed the PR accordingly.
Happy to receive another review. :-)

[tjorim]

Nice improvement, no more sed on the config.json to adjust the version 🎉