Skip to content

Questions for the previous API agent (paste as one message; post its reply back to MMDEP)

Context for the agent: Money Marche's API (GitLab moneymarche/api) and MM-Cron are being taken over by a new agent. Please answer from what you did and where you saved it; give repo, branch, file path, MR or issue number for every item. If you don't know, say "not known".

  1. Swagger / OpenAPI: Where did you save the swagger or OpenAPI documentation for the Money Marche API? Is it generated from code (which library) or hand-written? Which routes does it cover?
  2. Column documentation: Did you document the database tables and columns (data dictionary)? Where? Which tables are covered?
  3. Route inventory: Where is the full list of API routes with their parameters and response shapes? Which routes are used by the website (WordPress plugins), webapp-sakai, PE and MM-Cron?
  4. Direct database access: Which applications or scripts read or write the database directly instead of using the API? Where is that list?
  5. Duplicate and missing NAV records: What did you find about duplicate dates and gaps in NAV history (scheme and index)? Root cause, affected tables, scripts responsible, and any fix MRs.
  6. AMC master and factsheets: Which route and table serve the AMC (provider / product owner) list? Did you use AMFI's monthly factsheet links anywhere? Is any factsheet link hardcoded?
  7. Category flags: Why does /category return status and show-in-menu as 1 for every category? Where does the production website read the real flags, and how are hidden categories rolled up one level?
  8. stgapi: What is the state of stgapi (staging API) and its database? Why does it return 503? What is needed to bring it up?
  9. Secrets: Which credentials were found hard-coded (names only, never values), and which MRs move them to configuration?
  10. Open work: Which of your open MRs are still valid, which are superseded, and in what order should they be merged?
  11. Anything else the next agent must know that is not written in the repository.