Triggers created with Azure SDK not showing in data factory triggers list

Claude-Chantal Koundé 25 Reputation points
2023-07-19T16:50:45.64+00:00

I am trying to create programmatically triggers for my data factory with Azure SDK. My adf client runs well and creates the trigger, but it doesn't appear in my data factory UI or even on the associated devops.

When I execute adf_client.triggers.list, the created trigger appears, but it does not on the UI.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,209 questions
{count} votes

Accepted answer
  1. PRADEEPCHEEKATLA 90,536 Reputation points
    2023-07-20T08:58:57.9866667+00:00

    @Anonymous - Thanks for the question and using MS Q&A platform.

    Before, we get into your answer let me introduce some concepts in Azure Data Facotry:

    In Azure Data Factory there are two modes, GIT and Live mode.

    GIT mode reflects what is held in the GIT repo, it loads all objects using GIT as the source of truth. This is only available when you have a GIT /ADO integration.

    Live mode reflects what triggers and pipelines are running off of. This is updated on Publishing. The is the source of truth for anything running (except debug/sandbox).

    These two modes are separate. Only when the collaboration branch of GIT is published, is the Live mode updated to match the GIT mode.

    With these two modes and their relation explained, I now move on to how the CLI , Powershell, SDK, or API related.

    The CLI, Powershell, SDKs and REST API, all directly work on the Live mode. They have no way to interact with the GIT repo, and so have no affect on GIT mode. The only exception, is altering or removing the repo integration settings. Still, this doesn't change the repo, it only changes which repo will be used by the UI. User's image

    Only the UI can work with GIT mode. Only the UI can push changes to the repo. Only the UI can read from the repo.

    This means when you use the SDK, you are making a partial publish, and ignoring the GIT repo. This causes the two to fall out of sync and will likely cause problems later.

    This also means, the CLI is useful if for some reason you need to stop a trigger, but are not in a position to do a full publish. I advise against using the CLI to author while a GIT/ADO integration is present.

    For more details, refer to Source control in Azure Data Factory.

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.