Deployed feed version summaries

[br648]

Checklist

• Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
• Any modified or new methods or classes have helpful JavaDoc and code is thoroughly commented
• The description lists all applicable issues this PR seeks to resolve
• The description lists any configuration setting(s) that differ from the default settings
• All tests and CI builds passing

Description

A new end point has been added to the feed source controller to return the deployed feed version for a given feed source. If the project has a pinned deployment and this deployment has a feed version this is used. If not, the latest feed version for a feed source is used.

[br648]

@philip-cline I've reverted this back to using the previous approach of getting the deployed feed version with the feed source, so will work with the existing UI functionality. I'm still slightly concerned by how long this might take with 100+ feed sources. Please let me know how it performs!

[philip-cline]

This is looking good to me. It has sped things up for a large deployment to around 5s, which maybe isn't great but it's a start at least.

[miles-grant-ibigroup]

Working great! Just a few possibilities for speed improvements possibly, but I don't have any concrete suggestions so will approve while putting these ideas out there. Let me know what you think!

[miles-grant-ibigroup]

Why do we do this instead of a null check on deployedFeedVersion?

[br648]

This is to prevent calls to retrieveDeployedFeedVersion() where there are no deployed feed versions. Using null resulted in the following scenerio: Call to getDeployedFeedVersionId() returned null, followed by a call to getDeployedFeedVersionStartDate() returning null and a call to getDeployedFeedVersionEndDate() also returning null.

[miles-grant-ibigroup]

I think this may just be issues with my java understanding how is this field better than those 3 methods returning null? Is it to avoid mongo queries?

[br648]

Going to merge this to get the correct functionality to prod. Then look to include the project DB call into the two Mongo queries to further improve performance in a new PR.