Skip to content

v0.70.0 - 2025-06-04

Choose a tag to compare

View all tags
@vincent-olivert-riera vincent-olivert-riera released this 04 Jun 08:19
v0.70.0
7759654
This commit was signed with the committer’s verified signature.
vincent-olivert-riera Vicente Olivert Riera
GPG key ID: 925BD14E0CDAFF19
Verified
Learn about vigilant mode.

Warning

This release includes breaking changes. Make sure you read these release notes, specially the "Breaking changes" section at the bottom.

Changelog

  • [IMPROVEMENT] Make owner fields not nullable #581 ( ⚠️ breaking )
  • [IMPROVEMENT] Permission check for Alertmanager #595 ( ⚠️ breaking )
  • [IMPROVEMENT] Fix UI quirks in the Farm Register page #604
  • [IMPROVEMENT] Add 'Token' panel to UI #596
  • [IMPROVEMENT] Fix UI quirks in Farm detail page #602
  • [IMPROVEMENT] Set owner when adding external farms #599
  • [IMPROVEMENT] Improve the feature displaying data source load #597
  • [IMPROVEMENT] Preventing the browser from caching promgen.vue.js file #600
  • [IMPROVEMENT] Rename some buttons #598
  • [IMPROVEMENT] Disengage Farm Update from Project #594
  • [IMPROVEMENT] Use DRF's APIView for AlertReceiver API #591
  • [IMPROVEMENT] Fix LegacyKeyValueFormat warnings in Dockerfile #589
  • [CLEANUP] Delete the unused template file url_form.html #592
  • [BUGFIX] Fix external Farm linkage #605
  • [BUGFIX] Trim whitespaces of search input #593
  • [BUGFIX] "Home" link in some breadcrumbs redirects to "Services" page #588
  • [INTERNAL] Bump docker/build-push-action from 6.17.0 to 6.18.0 #601
  • [INTERNAL] Update CODEOWNERS #606
  • [INTERNAL] Bump docker/build-push-action from 6.16.0 to 6.17.0 #590
  • [INTERNAL] Bump docker/build-push-action from 6.15.0 to 6.16.0 #587
  • [INTERNAL] Bump actions/setup-python from 5.5.0 to 5.6.0 #586

Breaking changes

Owner fields not nullable

As we mentioned in the release notes for the previous release, the owner fields in the Service, Project, Sender and Farm objects could be null. This is not allowed anymore in this new release, so before updating please make sure all of those objects have an owner set.

Permission check for Alertmanager

If you are not using Promgen for routing alerts, this does not affect you.

From this release, Alertmanager will need a token to use Promgen's alert API. Typically, you configure some webhooks in Alertmanager to route alerts through Promgen. Now, those webhooks need to provide credentials.

As a first step, you need to go to Promgen's admin panel and create a new user account for Alertmanager. It doesn't matter which password you chose, since it won't be used at all. We recommend a user name like alertmanager_sa (which stands for Alertmanager Service Account), but you can chose any name you want.

Second step, you need to grant to that user account the promgen | alert | Can process alerts user permission.

Third step, you need to create a token for that user account.

With that token, you can now configure your Alertmanager's webhooks to provide credentials. Typically, in the alertmanager.yml file, you would have a receivers configuration similar to this one:

receivers:
  # Route alerts through Promgen
  - name: promgen
    webhook_configs:
    - url: <Your Promgen URL>/api/v1/alerts
      http_config:
        authorization:
          type: Token
          credentials: <The token you created on the third step>
Assets 2
Loading