Fix custom action with multiple overrides#96
Merged
Conversation
ec1933b to
3825818
Compare
3825818 to
aa96a8a
Compare
javi-null
approved these changes
Nov 27, 2025
pilundain
approved these changes
Nov 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Cada cliente puede agregar sus propias custom actions a un scope (por ejemplo el override de Scheduled Task agrega un Trigger Job).
Originalmente, cuando había un único layer de override, si necesitábamos ejecutar un action que no definía el Scope base (no existe el worfklow con el nombre del action), lo buscábamos directo en el path de overrides configurado.
Ahora que el overrides puede tener múltiples path, debemos recorrer los posibles overrides hasta encontrar el primero que define el action. Ese override se convierte en el base para la ejecución del acción.