When I set up my own ESAP that needs to talk to its own Rucio instance, I have to configure the URL both in the envrionment through the RUCIO_HOST and RUCIO_AUTH_HOST as well as in the esap/esap/esap_config.yaml
file which contains a url
and a user_url
. This is not really documented and may lead to some weird errors because the URL used to list the scopes is taken from the environment while the URL that is used to find the files within a scope is taken from the latter.
I am looking into this so I may propose a fix today.
When trying to connect ESAP to the SKAO Rucio, this failed because the aud
of the OIDC request is expected to be slightly different in this case. This is an extension of the original aud (adding an extra https://wlcg.cern.ch/jwt/v1/any
to it, but I think it may be nicer to make this configurable using an environment variable.
This is a “code smell” issue; not a need for an urgent fix.
@sarusso has written some ESAP installation instructions and published them at https://www.ict.inaf.it/gitlab/exact/ESAP. They look really helpful! Can we add them to / merge them with https://git.astron.nl/astron-sdc/esap-api-gateway/-/wikis/Build-&-Deploy-ESAP ?
I think this issue can be closed @swinbank Our documentation in both the wiki and ESAP Deployment are sufficient.
ESAP needs to be registered with the OSSR before the end of the project. Need to coordinate this with WP3.
ESAP has been filed with Zenodo at: https://zenodo.org/record/7585743
Closing this issue.
Only thing left todo would be to create an entry in Zenodo. First let's test it against their test instance to make sure the tokens are passed correctly.
To demonstrate the async query capabilities, write a simple async TAP query page and integrate it with ESAP. This is assumed to be independent of the existing VO query functionality (given the bugs on #175).
Great :) I think I will leave it as is now. There are many more ideas, but let's focus on something else for now.
Hooray!
I tried it. It works. It is a thing of beauty!
Anything else you want to get done before we close this issue down?
The demo GUI is merged and has been deployed! https://sdc-dev.astron.nl/esap-gui/jobs/13/
So let's shift the milestone.
...so let's shift the milestone.
...so let's shift the milestone.
...so let's shift the milestone.
We do not expect this to be done by the end of the ESCAPE project due to lack of resources, so I'm dropping it from the v1.0 release milestone... and shifting it to an assumed future v2.0! :-)
When credentials are provided, the Zooniverse connector should only return your own datasets, instead it returns all datasets.
Update the ESAP GUI dependencies (mainly react) and fix the warnings (un-used imports, useEffect
hook dependencies).
Make sure that running npm build
has no warnings (so we can remove the CI=
env variable)
Can not be made available for v1.0