Skip to content

Add TDeploy support for PDF service and Analysis info method#160

Open
bgelatti wants to merge 3 commits into
mainfrom
pdfServiceTdeploy
Open

Add TDeploy support for PDF service and Analysis info method#160
bgelatti wants to merge 3 commits into
mainfrom
pdfServiceTdeploy

Conversation

@bgelatti

Copy link
Copy Markdown
Contributor

Problem

  • PDF service was hardcoded to use production endpoints, not supporting TDeploy regions
  • Analysis class lacked a public method to retrieve analysis metadata (name, ID, status, run location)
  • TDeploy region validation logic was duplicated in codebase

Investigation

  • Found TDeploy validation code inline in getConnectionURI() that could be reused
  • Analysis internally used /info endpoint but didn't expose it publicly
  • PDF service needed dynamic endpoint resolution based on region configuration

Solution

  • Extracted getTDeployRegion() as reusable utility function in regions module
  • Added public info() method to Analysis class with proper AnalysisItem type
  • Integrated TDeploy region support in PDF service for dynamic endpoint selection

Changes

  • Analysis: New info() method returns analysis metadata
  • PDF Service: Dynamic endpoint resolution based on region (TDeploy or production)
  • Regions: Exported getTDeployRegion() utility for reuse across services

Added public info() method to retrieve analysis metadata including ID, name, run location, and active status.
…rvice

Extracted TDeploy region validation logic into reusable getTDeployRegion function. Updated PDF service to dynamically use TDeploy endpoints when configured.
Fixed JSDoc return description to accurately reflect that the function returns a TDeploy id string, not a RegionsObj.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants