-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not all recipe steps are being execute when executing a recipe from migration #14881
Comments
OrchardCore/src/OrchardCore/OrchardCore.Recipes.Core/Services/RecipeExecutor.cs Lines 156 to 158 in 9abd8ff
OrchardCore/src/OrchardCore/OrchardCore.Abstractions/Shell/Scope/ShellScope.cs Lines 320 to 332 in 9abd8ff
|
@jtkech thank you! I also tried this and it did not work (note how I run the features first (which should be it's own scope). The the second recipe would have used the newly enabled features.
|
Yes, but as long as you are using the recipe migrator, because of the following all recipes and their steps will run in the same shell scope.
|
Thank you @jtkech |
I have a recipe that is executed from a migration step. The recipe does multiple step. In summary here is what the recipe does
OrchardCore.Deployment
andOrchardCore.Search.Elasticsearch
)ElasticIndexSettings
this step supposed to create an elasticsearch index. This features required bothOrchardCore.Deployment
andOrchardCore.Search.Elasticsearch
to work.OrchardCore/src/OrchardCore.Modules/OrchardCore.Search.Elasticsearch/Startup.cs
Line 274 in 4f5a01d
But, for some reason the
ElasticIndexSettings
step never get called. If I make the recipe as a startup or parcial recipe, then everything works. @jtkech any idea why this recipe is failing when invoked from a migration?Here is the full recipe
That recipe existis in a file called
knowlegde-base.recipe.json
and is located inside the Migrations folder. Here it my migration step the invokes it.The text was updated successfully, but these errors were encountered: