Skip to content

Conversation

@jesusbv
Copy link
Collaborator

@jesusbv jesusbv commented Jul 3, 2025

Description

Refresh or update the instance data in the DB, before RMT 2.22 there was no need to do this
as the instance data was fresh from the client, after 2.22 we are using instance data from the DB
and we need to refresh that data

  • Related Issue / Ticket / Trello card:

How to test

Run a zypper up on a already registered instance with instance data on the DB and that instance data should get updated on the DB

Change Type

Please select the correct option.

  • Bug Fix (a non-breaking change which fixes an issue)
  • New Feature (a non-breaking change which adds new functionality)
  • Documentation Update (a change which only updates documentation)

Checklist

Please check off each item if the requirement is met.

  • I have reviewed my own code and believe that it's ready for an external review.
  • I have provided comments for any hard-to-understand code.
  • I have documented the MANUAL.md file with any changes to the user experience.
  • If my changes are non-trivial, I have added a changelog entry to notify users at package/obs/rmt-server.changes.

Review

Please check out our review guidelines
and get in touch with the author to get a shared understanding of the change.

@jesusbv jesusbv requested review from digitaltom and rjschwei July 3, 2025 13:33
@jesusbv jesusbv self-assigned this Jul 3, 2025
@jesusbv jesusbv added the 2.23 label Jul 3, 2025
@jesusbv jesusbv force-pushed the update-instance-data branch from b13c963 to 75f4bdd Compare July 3, 2025 14:28
@jesusbv jesusbv merged commit 93d0058 into master Jul 4, 2025
3 checks passed
@jesusbv jesusbv deleted the update-instance-data branch July 4, 2025 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants