suit-2022.2.1 built

Phalax updated to deploy on data-int

I have done some interactive testing of the portal running on data-int (v2022.2.1).

• The coverage map for a generic TAP search is the color HiPS map provided by Eli last week. Note that if you change away from that map, it's impossible to get back to our coverage map without starting from scratch. This is because we have not yet put a hipslist endpoint in place
• I have verified that all three example ADQL queries do run and return results. It appears that the "pan to catalog" functionality doesn't work as expected if there was a query done previously. If I x-out of the previous query, it does pan on the coverage map to the location of the results from the TAP query
• I've confirmed that the example coordinates on the default query page do all produced results. I'm not sure why we have an example of a name lookup if they aren't useful in this context, but maybe it was easier to do that than remove the name resolver button?

Thank you for the testing, Simon Krughoff!

Regarding the comments above:

1. It would be reasonable for there to be a way of restoring the default no matter what. I'll ask about that. I'll also file tickets for the HiPS list work.
2. I'd like a demo and/or steps-to-reproduce for the problem with pan-to-catalog. If there's a bug now is the perfect time to get it fixed; we're in release-candidate status for the next formal Firefly release in July.
3. I was torn about whether to include a name-resolver example; the name lookup is useful if someone decides to experiment with the TAP search on other real-sky TAP services. I certainly wouldn't remove the actual feature.