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
{{ message }}
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.
In order to truly support a distributed Mixer build, where templates and adapters come from far-flung repos, we need to auto-generate the nop and denier adapters.
Architecturally, we can chose to actually generate these adapters. Or it might be simpler to directly build those adapters into Mixer and make them slightly magical such that they can automatically be used with all known applicable templates. This might be considerably less work overall and would achieve the same goals. We should only do this option if it doesn't compromise our internal architecture in any significant way.
The text was updated successfully, but these errors were encountered:
In order to truly support a distributed Mixer build, where templates and adapters come from far-flung repos, we need to auto-generate the nop and denier adapters.
Architecturally, we can chose to actually generate these adapters. Or it might be simpler to directly build those adapters into Mixer and make them slightly magical such that they can automatically be used with all known applicable templates. This might be considerably less work overall and would achieve the same goals. We should only do this option if it doesn't compromise our internal architecture in any significant way.
The text was updated successfully, but these errors were encountered: