Skip to content

v0.6.2 - 2023-11-07

Compare
Choose a tag to compare
@Callum027 Callum027 released this 07 Nov 08:53
· 23 commits to main since this release
3d77e76

This is a backwards-compatible feature release that makes using multiple configuration files more flexible.

Buildarr allows you to split your configuration into multiple files using the includes option.

Before this release, however, there was a limitation to this functionality: each individual file had to be a valid configuration file on its own, and each file had to parse correctly when validated.

prowlarr.yml:

---

includes:
  - prowlarr-2.yml

prowlarr:
  instances:
    prowlarr:
      api_key: xxxx
      settings:
        indexers:
          indexers:
            definitions:
              "Nyaa.si":
                type: nyaasi
                enable: true
                sync_profile: Standard
                redirect: false
                priority: 15
                grab_limit: 50  # Overridden in the included file.
                query_limit: 10010
                fields:
                  torrentBaseSettings.seedRatio: null
                  prefer_magnet_links: true

prowlarr-2.yml:

---

prowlarr:
  instances:
    prowlarr:
      settings:
        indexers:
          indexers:
            definitions:
              "Nyaa.si":
                type: nyaasi  # Already defined, but must be defined here to work.
                sync_profile: Standard  # Already defined, but must be defined here to work as well.
                grab_limit: 104  # Override the value in the original file.

With this release, this limitation has now been eliminated. The above example can now be simplified to the following, and it will work as expected:

---

prowlarr:
  instances:
    prowlarr:
      settings:
        indexers:
          indexers:
            definitions:
              "Nyaa.si":
                grab_limit: 104  # Override the value in the original file.

This makes it possible to more freely structure your configuration files, e.g. splitting secret parameters (e.g. API keys and passwords) into a separate file from the main configuration.

For more information, check the configuration documentation.

Changed

  • Allow any configuration value to be defined in any file (#146)