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

GUI OPIs: Automate the gathering of OPIs into the server OPI repo #7093

Open
6 tasks
Tracked by #7088
KathrynBaker opened this issue Mar 18, 2022 · 0 comments
Open
6 tasks
Tracked by #7088

Comments

@KathrynBaker
Copy link
Member

KathrynBaker commented Mar 18, 2022

As someone developing OPIs for use in the IBEX client, I want to be able to get the OPIs from the server (see #6562 for the discussion) and to get the ones that match the version of the IOC in use where appropriate.

Acceptance Criteria

  • The OPI for one IOC has been moved from the server OPI repo into the appropriate support module
  • There is a method which on make of the IOC will copy that OPI into the server OPI repo for serving to the client
  • The OPI is still available in the client
  • Either the githooks for OPIs are applied to the appropriate support module or a different method of ensuring that behaviour is defined and enacted (this ticket is being created before that decision should be made)
  • A tech debt/umbrella ticket with a list of OPIs that can be moved into support modules is created, listing at least 10 more OPIs to be considered and the total of OPIs currently in the folder
  • The workflow is updated so that new OPIs are created in the appropriate support module

Notes

  • The creation of the ticket with the number of OPIs is so that we can consider them in a chunks, if we know there are 100 OPIs to consider, then rather than list all 100 only the first ten are listed, but that would be 10 out of 100, there would still be an indication that there are 90 more to look at.
  • OPIs that do not associate to a submodule should remain in the server OPI repo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant