You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We still read the host map/topology info from the backup bucket although it is stored in the MedusaBackup objects themselves.
It would be good to simplify our codebase and avoid unnecessary network calls by using the MedusaBackup status to read the host map from the backup cluster and use it to compute the restore mapping.
### Definition of Done
- [ ] Restore mapping is done by reading the MedusaBackup object status instead of invoking medusa through the GRPC server
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-28
The text was updated successfully, but these errors were encountered:
We still read the host map/topology info from the backup bucket although it is stored in the MedusaBackup objects themselves.
It would be good to simplify our codebase and avoid unnecessary network calls by using the MedusaBackup status to read the host map from the backup cluster and use it to compute the restore mapping.
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-28
The text was updated successfully, but these errors were encountered: