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
i was thinking about this as i was creating a high level test case for application-package builds (apgs):
Scenario Outline: Successful Application Package Builds
Given I have a token to authenticate with Unity Services
When I submit <repo_name> to the apgs build system
Then the apgs build response is <result>
And I wait for the apgs build to complete
And the completed apgs build information references <repository>
And the completed apgs build information references the application catalog
my initial thought is:
the request to the apgs should return a response almost immediately (e.g. success| failure and a job ID)
Job_id can be queried for status (accepted, in progress, success, failed) (thoughts?)
once the job is completed, a 'result' should be available, the result should contain:
Warnings/Errors (?)
the location of the artifact (e.g. built and published to dockerhub)
The location of the application pacakge files (e.g. dockstore)
Refocus task on using unity-app-generator #21 Dockerfied approach running within Airflow. Possibly a thin layer over OGC API usage in unity-sds-client.
Create an endpoint, possibly a AWS lambda, to provide build status information back to the user.
The text was updated successfully, but these errors were encountered: