service-fabric | Service Fabric is a distributed systems platform | Continuous Deployment library

Is there a way to get an Azure AD Service Principal ID with an in-built ARM template function? I'm looking for the ARM equivalent of Get-AzADServicePrincipal -DisplayName "Azure Service Fabric Resource Provider" and drawing a blank.

Context: I'm following a tutorial on deploying a Service Fabric managed cluster using an existing load balancer, and the tutorial requests that you run a powershell command to get the resource provider's service principal ID and then hard-code said ID in the ARM template. This ID is expected to vary by tenant, and the same template will be deployed to multiple tenants.

Is it possible to get a list of Operating Systems supported by Azure Service Fabric cluster in the PowerShell or Azure CLI?

Official Azure CLI documentation provides list of available OS: --os {UbuntuServer1604, WindowsServer1709, WindowsServer1709withContainers, WindowsServer1803withContainers, WindowsServer1809withContainers, WindowsServer2012R2Datacenter, WindowsServer2016Datacenter, WindowsServer2016DatacenterwithContainers, WindowsServer2019Datacenter, WindowsServer2019DatacenterwithContainers}

Portal has updated list of OS:

Official documentation provides a table of supported OS versions. link

The documentation looks outdated and it is difficult to determine the value of a parameter for the Azure CLI command from the parameter name.

I want to use "WindowsServer datacenter-core-1909-with-containers" but can't figure out the --os parameter value to achieve it.

For GDPR reasons, I need to ensure that I don't store customer data which I no longer need. When looking at Service Fabric Actors, I am uncertain what "garbage collection" really means.

All,

I have some problem setting up end-2-end transaction monitoring in ApplicationInsights, it seems to break the end-2-end view on my ServiceFabric ApiGateway service (.net CORE). This results in 2 traces in AppInsights instead of 1 (which I want ;-).

Ok my setup:

So an external API (.net core) which communicates to a ApiGateway (.net core stateless service) in a SF cluster via HTTP. Within the SF cluster all service (stateless full .net) communication is via Remoting V2.

I setup ApplicationInsights using ex. : https://github.com/yantang-msft/service-fabric-application-insights-example

In ApplicationInsights I see 2 traces (which should be one), being:

• a trace containing External API & ApiGateWay and the request to the stateless service
• a trace containing communication between the stateless services (which are multiple)

It looks like the "Operation Id" is not reused when sending the message from the APIGateway down. Is AppInsights i can see the "Operation Id" differ.

Does anyone have a idea? An I missing something? Should I set the operation id on the outgoing request in the ApiGateway (and how can I do that ;-))

I am attempting to try out Service Fabric on my local MacBook Pro running Docker Desktop. I'm following along with Microsoft's documentation located here: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-mac

When I go to launch the Docker container, I'm calling this command

This is a followup question to Specific questions about unit-testing Service Fabric Applications using Mocks

I am using Xunit along with ServiceFabric.Mocks to Unit Test my application. My Service Fabric application looks like this:

This question is a follow up to: Writing UnitTests for a Service Fabric Application Class

My application definition is of the type - simplified it to solve the most basic of problems I am facing:

I'm trying to run the sample script found here: https://docs.microsoft.com/en-au/azure/service-fabric/service-fabric-quickstart-containers-linux#create-a-service-fabric-cluster

I can't figure out how to use an AspNet Core 3.1 Web Api with Service Fabric and Autofac, and also how to have it ready for a TestServer to run for integration/functional testing.

The documentation is very incomplete.

Autofac documentation shows how to modify Program.cs to build autofac container, but it does not mention anything about the Startup.cs class that all the web api have: https://autofaccn.readthedocs.io/en/latest/integration/servicefabric.html

Also the only example that Autofac has for service fabric is not a web api: https://github.com/autofac/Examples/tree/master/src/ServiceFabricDemo

There are other questions without valid answers: Service Fabric AspNet Core 3.1 Autofac WebHostBuilder

Does anybody have any example on how to achieve this?

I can achieve the following (please see my GitHub repository with the sample)

• Service fabric with stateless AspNet Core WebApi project (dotnet core 3.1)
• Using Microsoft Dependency Injection to register services
• Using TestServer to run integration tests on the http endpoint, and able to overwrite dependency injection registrations in a clean way without having to create another Startup class

I want the exact same, but using Autofac as DI container.

UPDATE 1: I can't add Autofac to a WebHostBuilder and the ConfigureServices(IServiceCollection services) must be void as per AspNet Core 3.1+, so this is where I'm stuck. How to replace MS Dependency Injection in my sample