Closed jordanpadams closed 4 months ago
Related: this pull request
📆 September status: Work is underway with final implementation and testing completing this sprint, and deployment planned for next sprint.
Related: this pull request
Status: @nutjob4life working on tagging and releasing these with roundup
Related: this pull request (yes, there are more and more of these!)
📆 October status: Implementation completed. Running into bugs testing on staging machines, but still on schedule for production deployment at end of sprint.
📆 November status: Deployment delayed 1 sprint due to permissions issues. Expected completion in January. This is an operations task so no impact on overall system delivery.
📆 December status: Testing in progress. This is an operations task so no impact on overall system delivery.
📆 01/2024 status: delayed due to IT Security concerns needing to be addressed. https://github.com/NASA-PDS/search-ui-legacy/issues/5 is pending. no impact on delivery,
Waiting for response of the SAs (DSIO-4952)
Unblocked by SSL issue we were seeing in Tomcat. New DSIO-5364 ticket created to update reverse proxies to connect with UI.
Jordan also fixed a quick bug and is working next on getting reverse-proxies set up to test with UI.
I think this is actually finally done! only catch is search-ui-legacy release is failing for some reason, but I think that is an issue with GitHub, and I just built and tagged locally for now. https://github.com/NASA-PDS/search-ui-legacy/actions/runs/8013573311
But here is what the keyword search now looks like hooked up to search-ui-legacy:
NOTE: Looks like there is no PDS3 data. so we need to reload all of that.
💡 Description
Vulnerability identified on operational services. Need to fix and upgrade:
For PDS4 data
Services impacted
For PDS3 data
Indirectly related downstream:
Sub-tasks