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
As a container Service User I want to re-use identical containers so I can conserve resources
Assumptions
FuncX web service will compute a hash of the container spec
The hash will be done after some basic standardizations (sort the lists) - this will increase the likelihood of matching up identical containers
The hash will be saved in the container table
New container requests will have a hash computed. If the hash matches and the build status of that container is ready then just return the container UUID of the previous container request
If no successful match is found, go ahead and pass the request on to the container service.
Acceptance Criteria
Given I have successfully build a container for a spec When I submit a container build request for a functionally identical spec Then the container service is not invoked And I receive the UUID of the previously built container
Given I have successfully build a container for a spec When I submit a container build request for a different spec Then the container service is invoked And I receive a new UUID for the new container
The text was updated successfully, but these errors were encountered:
As a container Service User I want to re-use identical containers so I can conserve resources
Assumptions
ready
then just return the container UUID of the previous container requestAcceptance Criteria
Given I have successfully build a container for a spec When I submit a container build request for a functionally identical spec Then the container service is not invoked And I receive the UUID of the previously built container
Given I have successfully build a container for a spec When I submit a container build request for a different spec Then the container service is invoked And I receive a new UUID for the new container
The text was updated successfully, but these errors were encountered: