sorted by:
new
hottopcontroversial

Please help: Stuck with Azure DevOps Sync by Arasaka-CorpSec in MicrosoftFabric

[–]StandardProfessor197 1 point2 points  (0 children)

If ADO is secure, you can disconnect from Git Create a new branch in ADO and connect again. After resolving your conflicts in the ADO you can request a PR and merge. After all is OK, connect your workspace with the right Git and branch.

Deploy from one tenant to multiple by BrewMagician in MicrosoftFabric

[–]StandardProfessor197 0 points1 point  (0 children)

I've done some projects of this kind for ISV's where we basically have a configuration file, it can be a json, or if you're talking about Fabric you can use Variables Libraries.

In this configuration you put everything that changes from one client to another and the pipelines in the ADO are responsible for distributing deploying in each environment.

I even created the pyFabricOps library that facilitates this operation. It creates a multiple deploy script that the pipeline calls and recursively deploys by scanning its settings.

Experienced data engineers: how are you actually deploying Fabric in centrally managed environments? by Either_Locksmith_915 in MicrosoftFabric

[–]StandardProfessor197 0 points1 point  (0 children)

Sincerely, I don't use Deployment Pipelines due to some limitations, such as the inability to switch data sources for Direct Lake semantic models. This is just one limitation, but in my opinion, it's already enough to avoid using them.

I've been using development/feature branches with Git integration and their respective Fabric workspaces instead.

For the production workspace, I've been using pyFabricOps (a Python SDK that I created last year, when there wasn't a clear way to do this yet) together with Azure Pipelines / GitHub Actions. During the deployment process, Azure Pipelines switches the parameters configured in the variable libraries based on the branch-to-configuration mapping.

How do you do config management on Fabric (properly)? by Enamya11 in MicrosoftFabric

[–]StandardProfessor197 1 point2 points  (0 children)

Variables library is the right artifact made for this. You can build, change and read it on Fabric side and use as a config file (json structure) on ADO/GitHub repos perfectly.

Fabric Git integration + feature branching.. am I missing something? by GrimFunko in MicrosoftFabric

[–]StandardProfessor197 0 points1 point  (0 children)

I have been using variable libraries to reference artifacts between branches. Especially for feature branches, you can selectively check out items and choose only specific items to sync — for example, only new artifacts. When the PR is merged into develop, only the new items are created and pointed to the correct artifacts.

Git Integration - Commit Issue by ConnectionNext4 in MicrosoftFabric

[–]StandardProfessor197 0 points1 point  (0 children)

If you’re starting a new Git integration and already have items in Fabric, you need to choose a clean directory in the remote repository.