You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Although the pipelines are registered with the same key, they are distinct instances.
142
+
// One is generic, the other is not.
143
+
_pipeline=pipeline;
144
+
_genericPipeline=genericPipeline;
145
+
}
146
+
}
147
+
```
148
+
<!-- endSnippet -->
149
+
150
+
> [!NOTE]
151
+
> The resilience pipelines are registered in the DI container as transient services. This enables the resolution of multiple instances of `ResiliencePipeline` when [complex pipeline keys](#complex-pipeline-keys) are used. The resilience pipeline is retrieved and registered using `ResiliencePipelineProvider` that is responsible for lifetime management of resilience pipelines.
152
+
103
153
## Deferred addition of pipelines
104
154
105
155
If you want to use a key for a resilience pipeline that may not be available
@@ -133,6 +183,9 @@ services
133
183
```
134
184
<!-- endSnippet -->
135
185
186
+
> [!NOTE]
187
+
> The `AddResiliencePipelines` method does not support keyed services. To enable the resolution of a resilience pipeline using keyed services, you should use the `AddResiliencePipeline` extension method, which adds a single resilience pipeline and registers it into the keyed services.
188
+
136
189
## Dynamic reloads
137
190
138
191
Dynamic reloading is a feature of the pipeline registry that is also surfaced when
0 commit comments