Notiz
Zougrëff op dës Säit erfuerdert Autorisatioun. Dir kënnt probéieren, Iech unzemellen oder Verzeechnesser ze änneren.
Zougrëff op dës Säit erfuerdert Autorisatioun. Dir kënnt probéieren, Verzeechnesser ze änneren.
The following article details the file structure for Activator once they're synced to a GitHub or Azure Devops Repository.
Folder structure
Once a workspace is synced to a repo, you see a top level folder for the workspace and a subfolder for each item that was synced. Each subfolder is formatted with Item Name.Item Type
Within the folder for the activator, you see have the following files:
- Platform: Defines fabric platform values such as Display Name and Description.
- Properties: Defines item specific values.
Here's an example of what the folder structure looks like:
Repo
- Workspace A
- Item_A.Reflex
- .platform
- ReflexEntities.json
- Item_A.Reflex
- Workspace B
- Item_C.Reflex
- .platform
- ReflexEntities.json
- Item_C.Reflex
Activator (also called Reflex) files
The following files are contained in a Reflex folder:
.platform
The file uses the following schema to define an activator:
{ "$schema": "https://developer.microsoft.com/json-schemas/fabric/gitIntegration/platformProperties/2.0.0/schema.json", "metadata": { "type": "Reflex", "displayName": "displayNameGoesHere" }, "config": { "version": "2.0", "logicalId": "4f6a991f-721e-45c6-ba5a-ae09ad2897f2" } }ReflexEntities.json
This file has an array of JSON objects. We'll publish the schemas soon.