-
Data contracts. Building universal data access proxy api
Data contracts usually requires us to build around them a universal data access proxy API for users to consume. API utilizing proper data contracts, negotiated with different teams, acts as a unified gateway providing the necesities. Allows access to data sources like databases, REST APIs, GraphQL endpoints or other file systems. One api to rule them all Steps to build data contracts for proxy api You could try and adopt a similar flow for creating such access points, even make a template in JIRa so You will know where to get proper data and how to acquire it… or maybe expose the library and just aprove properly looking merge requests……
-
GIT token access issue – use special API url !
GIT token access issue will usually be that You are using a wrong url. When accessing files through the GitLab API using an access token you must use a special API URL, not the regular browser URL you see in firefox when navigating the repository. Using the standard browser URL will not work with API authentication tokens. Why Use the API URL? The regular repository URLs are designed for web browsers and do not support token-based authentication. (They could, but they just don`t :)) The GitLab API requires you to call its specific endpoints, which accept access tokens and return the raw file data or JSON metadata. URL Comparison Parameter…
