A ClowdEnv definition should deploy the mocks applications and allow you to turn on/off each of these:
the local UI
mock SSO
mock RBAC
mock entitlements
mock BOP
For the UI, at this time we can deploy 'gateway' and 'front-end-aggregator' service sets from e2e-deploy – OR we can deploy the new container-based UI that was worked on in the hack-a-thon if that is ready for use. Similar to deploy/deploy.sh, the operator will need to:
re-point all services (including gateway, if that is in use) to the mock RBAC/entitlements/BOP APIs if they are deployed
re-point the front-end to use the mock SSO if it is deployed
Integrate with the Clowder operator.
A ClowdEnv definition should deploy the
mocks
applications and allow you to turn on/off each of these:For the UI, at this time we can deploy 'gateway' and 'front-end-aggregator' service sets from e2e-deploy – OR we can deploy the new container-based UI that was worked on in the hack-a-thon if that is ready for use. Similar to
deploy/deploy.sh
, the operator will need to: