Investigate force check usage for pmm update (if removal possible)

Description

Currently in version 3 the usage of the force parameter is incorrect (force=true used on background and panel, force=false used on updates page).

Acceptance criteria

  • Background checks and update panel should use call with force=false

  • Updates page should use parameter with force=true

  • Reduce cache time (BE)

Steps to reproduce

  1. Login to PMM

  2. Open network tab

  3. Do one of the following:

    1. Reload page

    2. Check for an update from panel (not forced)

    3. Open updates page (PMM Configuration → Updates)

    4. Check for updates from the update page

Expected

The api call to /v1/server/updates on background and update panel should be called with ?force=false.
The api call to /v1/server/updates on updates page should be called with ?force=true.

Actual

The force parameter is currently used the other way around:

  • The api call to /v1/server/updates on background and update panel is called with ?force=true.

  • The api call to /v1/server/updates on updates page is called with ?force=false.

How to test

FB:

How to document

None

Activity

Nailya Kutlubaeva April 15, 2025 at 8:51 AM

verified

Details

Assignee

Reporter

Priority

Components

Labels

Needs QA

Needs Doc

Planned Version/s

Fix versions

Story Points

Sprint

Smart Checklist Progress

Start date

Created October 21, 2024 at 1:28 PM
Updated 22 hours ago