🎯 Summary

PIMS-426

Changes

Creating route for LTSA GET request.
Currently uses a stub response. Recommend using this until the controller logic is completed at a later date.

Testing

Using a token from PIMS, call the api/v2/ltsa/land/title endpoint. Should get a 501 response.

Future Work

• Need to determine how Keycloak will be handled in future integration tests. Currently in conversations with the SSO team on this. Update: They recommend mocking any of the authentication. I added an example of how to add user info into a Request in the unit test. Not sure yet if we can mock the entire keycloak package. Might need to just do a bypass of it entirely.
• Need to be specific in which roles can access this route. Right now it is all of them.

🔰 Checklist

• I have read and agree with the following checklist and am following the guidelines in our Code of Conduct document.

• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation where required.
• I have tested my changes to the best of my ability.
• My changes generate no new warnings.