SPIKE: Design an approach to export/import DI profiles

RCA Group

None

Description

We have different environments such as bugfest, ptf, rancher, hosted envs and on each environment different profiles configured. Sometimes profile configuration is difficult and time consuming to re-create on another environment, that can be useful for reproducing issue for example from ptf on hosted env, where we have more access permissions and monitoring tools.

There are 2 options available:

  • If it also  would be useful for librarians, for example to be able to export profiles configuration in text file and then import on another environment - its bigger effort including designing approach of file structure, UI/BE effort to upload/download file etc.

  • It will be used only  be developers/testers. In this case it can be some SQL job that migrates appropriate records from job, action, mapping profiles tables to another DB host

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Olamide KolawoleJanuary 6, 2023 at 9:15 PM

Spike has been documented here: https://folio-org.atlassian.net/wiki/x/v1IV

Ann-Marie BreauxMay 4, 2022 at 11:26 AM

Hi I moved this out of Morning Glory to reduce scope. Based on the description in this spike, it seems like we would need a feature to accomplish this work, especially since librarians have expressed interest in it as well. One of the complications is that different environments have different reference data, so the profiles sometimes need adjusting. For example, if the first environment has a certain location value that is being assigned in a Holdings field mapping profile, and the second environment does not have that location value, what happens? Permanent location is a required value for holdings records, so we would need to account for it somehow.

How important do you feel this is for the devs who are testing performance and functionality in various environments? At this point, my preference would be to move it from Morning Glory to "Not scheduled" rather than trying to include it in Nolana. What do you think?

cc:

Ann-Marie BreauxFebruary 2, 2022 at 2:52 PM

Needs to be its own feature - and use this as the feature or initial research spike

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Release

Quesnelia (R1 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 18, 2021 at 1:59 PM
Updated October 10, 2023 at 5:59 PM
Resolved January 6, 2023 at 10:20 PM
TestRail: Cases
TestRail: Runs