Skip to main content
Solved

CI/CD Pipeline for FME Flow Overwrites Deployment Parameters – Bug or Misconfiguration?

  • November 13, 2025
  • 1 reply
  • 110 views
peterhavik
Contributor
Forum|alt.badge.img+4

We are implementing a CI/CD pipeline for FME Flow using an Azure YAML pipeline. When exporting an FME project from DEV with deployment parameters enabled under Advanced Options, those parameters overwrite the values in ACC and PRD during deployment. If the same project is imported manually, this issue does not occur.

  • Is this a known bug in the FME Flow API?
  • Or is there a recommended way to prevent deployment parameters from being overwritten during automated deployments?

Additional details:

  • If all advanced options are manually unchecked, deployments work as expected.
  • The token used for the pipeline requires full permissions (fmesuperuser); otherwise, roles cannot be deployed. Restricting permissions or deployment parameter rights results in nothing being deployed.

FME Flow version we have is 2024.1.2

Any insights or best practices would be appreciated!

Best answer by evieatsafe

Thanks for your question ​@peterhavik! Looks like you submitted a support ticket about this as well. For anyone else coming across this in the future, I will summarize the resolution below.

The recommended solution is to migrate to the FME Flow REST v4 API. The v4 API handles this correctly by automatically excluding deployment parameters during import. The v3 endpoint has entered its deprecation phase as of FME Flow 2025.1 and is planned for removal in 2026.1, so upgrading is the path forward regardless.

A couple of things to be aware of when moving to v4:

  • The older beta endpoints (/fmeapiv4/migrations/imports/upload?skipPreview=true and /fmeapiv4/migrations/imports/$id/run) have been removed from the stable v4 release and will return a 404. Use the stable v4 endpoints instead.
  • Documentation available here: https://docs.safe.com/fme/html/fmeapiv4/docs/index.html

In the meantime, if you need a short-term workaround on v3, you can uncheck the "Include Deployment Parameters" option during manual export. This method is prone to human error which is why migrating to v4 is a better long-term fix.

Happy FMEing!

    1 reply

    evieatsafe
    Safer
    • evieatsafeSafer
    • Safer
    • Best Answer
    • May 5, 2026

    Thanks for your question ​@peterhavik! Looks like you submitted a support ticket about this as well. For anyone else coming across this in the future, I will summarize the resolution below.

    The recommended solution is to migrate to the FME Flow REST v4 API. The v4 API handles this correctly by automatically excluding deployment parameters during import. The v3 endpoint has entered its deprecation phase as of FME Flow 2025.1 and is planned for removal in 2026.1, so upgrading is the path forward regardless.

    A couple of things to be aware of when moving to v4:

    • The older beta endpoints (/fmeapiv4/migrations/imports/upload?skipPreview=true and /fmeapiv4/migrations/imports/$id/run) have been removed from the stable v4 release and will return a 404. Use the stable v4 endpoints instead.
    • Documentation available here: https://docs.safe.com/fme/html/fmeapiv4/docs/index.html

    In the meantime, if you need a short-term workaround on v3, you can uncheck the "Include Deployment Parameters" option during manual export. This method is prone to human error which is why migrating to v4 is a better long-term fix.

    Happy FMEing!

    Happy to help - Evie

    Community Stats

    32,545
    Posts
    123,579
    Replies
    40,792
    Members
    Terms & ConditionsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.