Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export and Import Context Should be Properties Based #90

Open
baubakg opened this issue Aug 31, 2022 · 0 comments
Open

Export and Import Context Should be Properties Based #90

baubakg opened this issue Aug 31, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@baubakg
Copy link
Member

baubakg commented Aug 31, 2022

The export and import of the context is currently tightly coupled with files.

When the producer phase is finished, we create a file (containing properties), which is then used by the databroker for exporting wherever we want.

The basic Idea is to let the user decide this, and:

  • The methods PhasedTestManager.exportPhaseData(), PhasedTestManager.fetchExportFile(), PhasedTestManager. exportContext(File), should all deal with a Properties object
  • The methods PhasedTestManager.importPhaseData(), PhasedTestManager.importContext(), should all deal with a Properties object
  • The interface PhasedDataBroker should be Properties driven (No ore use of files). This involves both store and fetch
    ** Deprecate the file ones and create a fetch and a store using a Properties Object.
  • Instead of storing the context by files, by default, we will use a, provided databroker that is file driven. When no databroker is set this is used
  • importPhaseData(), importContext()
@baubakg baubakg added the enhancement New feature or request label Aug 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant