Skip to content

Releases: grafana/oncall

v1.1.5

24 Nov 14:18
c53face
Compare
Choose a tag to compare

Fixed

  • UI bug fixes for Grafana 9.3 (#860)
  • Bug fix for saving source link template (#898)

v1.1.4

23 Nov 13:00
d50db0d
Compare
Choose a tag to compare

Fixed

  • Bug fix for #882 which was causing the OnCall web calendars to not load
  • Bug fix which, when installing the plugin, or after removing a Grafana API token, caused the plugin to not load properly

v1.1.3

22 Nov 18:37
bd27584
Compare
Choose a tag to compare
  • Bug Fixes

Changed

  • For OSS installations of OnCall, initial configuration is now simplified. When running for local development, you no longer need to configure the plugin via the UI. This is achieved through passing one environment variable to both the backend & frontend containers, both of which have been preconfigured for you in docker-compose-developer.yml.
    • The Grafana API URL must be passed as an environment variable, GRAFANA_API_URL, to the OnCall backend (and can be configured by updating this env var in your ./dev/.env.dev file)
    • The OnCall API URL can optionally be passed as an environment variable, ONCALL_API_URL, to the OnCall UI. If the environment variable is found, the plugin will "auto-configure", otherwise you will be shown a simple configuration form to provide this info.
  • For Helm installations, if you are running Grafana externally (eg. grafana.enabled is set to false in your values.yaml), you will now be required to specify externalGrafana.url in values.yaml.
  • make start will now idempotently check to see if a "127.0.0.1 grafana" record exists in /etc/hosts (using a tool called hostess). This is to support using http://grafana:3000 as the Organization.grafana_url in two scenarios:
    • oncall_engine/oncall_celery -> grafana Docker container communication
    • public URL generation. There are some instances where Organization.grafana_url is referenced to generate public URLs to a Grafana plugin page. Without the /etc/hosts record, navigating to http://grafana:3000/some_page in your browser, you would obviously get an error from your browser.

v1.1.2

18 Nov 09:56
a704c05
Compare
Choose a tag to compare

Bug fixes

v1.1.1

16 Nov 11:14
2c384ef
Compare
Choose a tag to compare
  • Compatibility with Grafana 9.3.0
  • Bug Fixes

v1.1.0

10 Nov 14:12
f6e2861
Compare
Choose a tag to compare
  • Release new schedules UI

v1.0.52

09 Nov 18:22
f6e2861
Compare
Choose a tag to compare
  • Allow use of API keys as alternative to account auth token for Twilio
  • Remove grafana_plugin_management Django app
  • Enable new schedules UI
  • Bug fixes

v1.0.51

05 Nov 07:23
144abaa
Compare
Choose a tag to compare
  • Bug Fixes

v1.0.50

03 Nov 18:45
fee1235
Compare
Choose a tag to compare
  • Updates to documentation
  • Improvements to web schedules
  • Bug fixes

v1.0.49

01 Nov 14:58
93cb36c
Compare
Choose a tag to compare
  • Enable SMTP email backend by default
  • Fix Grafana sidebar frontend bug