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
This week will see a rollout of the new Continuous Quality Control pipelines on the DataHUB. This means that all ARCs using the old validation pipelines will need an update that moves them to using the new validation_packages.yml config file to opt-in for user-selected validation packages.
While POCs of this exist across the ARCtrl stack and a manual migration guide will be uploaded, the ARCitect as the central tool must support this feature to some extent on launch. This will be on 2024-07-10, so time is of essence.
I suggest we only ship a bare-bones editing feature for this file to make the deadline here. This means:
ARCtrl:
Data model for validation packages
Reader/Writer functions for the file
Top-level API
ARCitect:
Simple key-value UI component that maps the allowed keys specified here and makes their values editable
I will take care of the ARCtrl side and update this issue with usage examples of the API. I suggest that the UI component can be created in parallel, with the backend using the new API once provided.
The text was updated successfully, but these errors were encountered:
Hi everyone, f17eb22 adds this functionality, specifically:
ARCitect now has a "Validation" item in the left menu which opens the new ValidationView (see below).
In this view users can choose to validate against the arc specification with a specific version (currently there is only one option).
They can also choose or enter custom validation packages where swagger provides suggestions for names and corresponding versions (currently there exists only one custom target but with several versions).
On pressing the save button the form will be converted into a YML file and stored in arc_root/.arc/validation_packages.yml.
When the Validation View is opened ARCitect will look for an existing YML file and populate the form accordingly.
Still needs to be tested
Currently all this functionality is implemented in ARCitect and does not use ARCtrl. I will close the issue for now and open a new issue to keep track of moving this functionality to ARCtrl.
This week will see a rollout of the new Continuous Quality Control pipelines on the DataHUB. This means that all ARCs using the old validation pipelines will need an update that moves them to using the new
validation_packages.yml
config file to opt-in for user-selected validation packages.While POCs of this exist across the ARCtrl stack and a manual migration guide will be uploaded, the ARCitect as the central tool must support this feature to some extent on launch. This will be on 2024-07-10, so time is of essence.
I suggest we only ship a bare-bones editing feature for this file to make the deadline here. This means:
I will take care of the ARCtrl side and update this issue with usage examples of the API. I suggest that the UI component can be created in parallel, with the backend using the new API once provided.
The text was updated successfully, but these errors were encountered: