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
To be able to have a single git repo that has multiple proivdes methods including the onboarding command mapper overloads
Observed Behavior
The overload isn't actually taking affect unless a dedicated git repo in NB is created for the onboarding mappers overload and ONLY that single provides is used.
Steps to Reproduce
Create git repo with multiple provides (config-context, onboarding mapping overrides)
sync repo
notice the overloaded yaml files arent actually taking into affect.
The text was updated successfully, but these errors were encountered:
I've tracked this down to being related to the check of GitRepository objects here. I think this should most likely be rewritten to be an icontains instead of looking for ONLY the command mapper ContentType. It might also be worth refactoring to allow for more than one GitRepo with that ContentType to be loaded.
Multiple repos with that content-type would require quite a bit of effort, most likely introducing some kind of "weighting", otherwise if two repos provide the same template/command mapper how do you pick the winner?
That's a fair point I hadn't thought of. I was thinking more of differing departments working on different command mappers. If they used the same Platform that would certainly be an issue.
Environment
Expected Behavior
To be able to have a single git repo that has multiple proivdes methods including the onboarding command mapper overloads
Observed Behavior
The overload isn't actually taking affect unless a dedicated git repo in NB is created for the onboarding mappers overload and ONLY that single provides is used.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: