buildpipeline | powered serverless build , test and deploy pipeline ft | Infrastructure Automation library

Tested here on a new project with pipeline1 and pipeline2. Pipeline2 successfully triggered when pipeline1 completes.

Possibly a bug with your project/azure devops. Try renaming the source pipeline and updating the trigger to the new value and see if that helps.

Make the DbSet public:

The error is pretty clear:

Circular component dependency detected

Your AfterSaleService depends on IOrderService and OrderService depends on IAfterSaleService which for obvious reasons will make it impossible for DI container to resolve the dependencies during construction. Personally I try not to inject dependencies of the same "level", i.e. repositories does not accept repositories, services - services and controllers do not depend on the other controllers so my recommendation would be to refactor your application so you don't need such injections (maybe introduce one more layer or move common code to static helpers or something else).

If it is not feasible ATM to rewrite due to amount of work you can use work around the issue for now - inject same level dependencies as Func's. Autofac provides Func resolutions out of the box (i.e. if you register IService you can resolve Func without any extra registrations), so you can do something like this:

Your applyMerchantRules method is non-static, therefore the lambda captures the enclosing this instance. Seems that you've made FraudDetectionRun serializable in an attempt to fix this, but you should rather make the applyMerchantRules static.

Don't change your SeedTestData method. Because it's responsible for seed your test data. You don't need to add TenantTestDataBuilder to seed your tenant-related data. It's also responsible for that too.

AWS has resolved the issue in jsii.

https://github.com/aws/jsii/issues/2963

It should be available with CDK 1.121.0.

The question is, other than the predefined variables (list here), is it possible to publish a custom variable in the first pipeline so it's available later as a resource variable?

I am afraid there is no such directly way to publish a custom variable in the first pipeline as a resource variable at this moment.

As workaround, we could use the REST API in the rescource pipeline to update the variable in the Variables tab for the current pipeline.

Steps:

• Define a variable in the later pipeline definition Variable.

• Add a task to invoke REST API (Definitions - Update) in rescource pipeline to update the value of the above variable in the later release pipeline.

• Use the updated value of the later pipeline variable in the later pipeline.

The details info about using REST API to update the value of the definition variable, you can follow the below ticket:

How to modify Azure DevOps release definition variable from a release task?

or you could use the Azure CLI to update the variable:

DependencyResolutionException: None of the constructors found with 'Autofac.Core.Activators.Reflection.DefaultConstructorFinder' on type 'Smart_Industrial_Management.Persistence.UnitOfWork' can be invoked with the available services and parameters: Cannot resolve parameter 'Smart_Industrial_Management.Persistence.SIMContext context' of constructor 'Void .ctor(Smart_Industrial_Management.Persistence.SIMContext)'.

It looks like you haven't register SIMContext when configuring the Autofac. Adding the following registration in your Configure method may help:

The problem is that EntityDisplay<>.Params is a value type - a struct. Change it to a class and you'll be fine.

Due to the way DI and reflection and whatnot all currently come together, we have to be able to cast the output of a reflection-based operation to an object. You can see the current wire-up code here. Unfortunately, the constructor invoker for a value type doesn't return an object so we can't resolve it and everything falls apart.

We'd likely accept a pull request with fix-up code for that, however DI into value types isn't usually something folks do.

Anyway, switch to class and it works.

As an aside, this was sort of difficult to walk through - in future questions it might help to reduce the repro a bit (e.g., you don't need the Holder class at all, it's just noise; you don't need the Verifiers, etc. Getting a cleaner format on the exception message in the question would also help, and be sure all the inner exceptions are included. The big key was the inner exception pointing at the constructor invoker. I was only able to see it by copy/pasting this code in and debugging, which, unfortunately, I normally don't have time to do. I'd have had to pass on answering this one otherwise.