>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3632000. --> Reported by: [szymon.zawadzki](https://www.drupal.org/user/3872487) >>> <p>TMGMT LATW Cloud connects the <a href="https://www.drupal.org/project/tmgmt">Translation Management Tool (TMGMT)</a> to LATW Cloud, a paid AI translation service. It translates content entities (with embedded entities such as Paragraphs), configuration (with <code>tmgmt_config</code>) and interface strings.</p> <p>The module is a connector. The AI model, prompt, glossary, budgets and target languages are set in the LATW Cloud panel, and translations are ordered there. LATW Cloud then calls a small signed API on the site to read the source of the items chosen for translation and to write the translations back:</p> <ul> <li>Content and configuration translations are saved through TMGMT jobs (one job per item and language, accepted automatically). Content Moderation states are respected.</li> <li>Interface strings are saved as customized locale translations, so <code>.po</code> imports do not overwrite them.</li> <li>Aborting or deleting one of these jobs in TMGMT cancels the item in LATW Cloud.</li> </ul> <p><strong>How it differs from similar projects</strong></p> <p><a href="https://www.drupal.org/project/tmgmt_deepl">TMGMT DeepL Integration</a> and <a href="https://www.drupal.org/project/ai_tmgmt">AI Translation Management</a> are TMGMT translators: a job is requested in the TMGMT checkout and sent to a machine translation API with the settings of the translator. With this module, translations are configured and ordered in the LATW Cloud panel. Prompt, glossary, context and budgets are kept in one place, and the whole site can be translated in bulk. TMGMT is used to save the translations, and Drupal stays the source of truth for content and translation status.</p> <p><strong>Notes for reviewers</strong></p> <ul> <li>Nothing is sent to LATW Cloud before an administrator clicks "Connect with LATW" at <code>/admin/tmgmt/latw</code> (permission <em>administer tmgmt</em>; the admin routes are POST-only and CSRF-protected). Pairing uses PKCE.</li> <li>LATW Cloud calls <code>POST /latw/v1/cloud/{endpoint}</code>. A custom access check (<code>SignatureAccessCheck</code>) lets in only requests signed with HMAC-SHA256 with the site's secret, with a timestamp window and a single-use nonce.</li> <li>The secret is not stored in configuration. It is kept in the State API, encrypted with AES-256-GCM using a key derived from the site's hash salt.</li> <li>Outgoing requests use Drupal's <code>http_client</code> with timeouts and redirects disabled.</li> <li>GitLab CI is enabled and green on 1.0.x: <a href="https://git.drupalcode.org/project/tmgmt_latw/-/pipelines">pipelines</a>.</li> </ul> <h3>Project link</h3> <p><a href="https://www.drupal.org/project/tmgmt_latw">https://www.drupal.org/project/tmgmt_latw</a></p>