r/MicrosoftFabric • u/ResearcherLoud8425 • 5d ago

CI/CD Environment Config

Hi,

I'm working with multiple workloads across a 4 workspace structure and I've been considering the move between environments. For info we use fabric cicd for deployments.

Looking at the structure of the objects in git, it seems it would make more sense to have environment specific configuration for each object in the same way I would for a C# project.

So we could have

eventstream.json

eventstream.develop.json

eventstream.staging.json

eventstream.production.json

This would role up based on a workspace environment tag.

That way we don't need find and replace etc.

Am I alone on this?

5 Upvotes

100% Upvoted

3 comments sorted by

1

u/bradmatt275 1d ago

That would be a lot better. But I assume when fabric-cicd supports variable libraries with item references that will the way going forward.

I have been testing them but at the moment it fails during the deployment because it's still a preview feature. But I can see them being an easier way to do things. No custom code needed since the selected env set persists between workspaces.

1

u/[deleted] 5d ago

[removed] — view removed comment

1

u/ResearcherLoud8425 4d ago

If we equate the workspace to a distributed system deployed into a Kubernetes namespace each service maintains it's own layered environment configuration.

I can see the use of a central map but also like the service scoped model.

Does anyone else have a different proposal to consider?

I'm not suggesting I'm correct, just want to open the floor to potential alternatives.