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 Dec 4, 2017. It is now read-only.
there's a number of boosters that don't work on OSIO right now; rather than making a branch and forking the whole catalog and deleting stuff, I'm wondering if some kinda filter file with patterns for including/excluding missions/runtimes/boosters to filter out might be the simplest approach to filtering stuff out?
i.e. to avoid loads of git issues as we try do keep doing PRs against different branches/forks for boosters that may be excluded for, say, OSIO but not for, say, on premise OSCP or OSD.
Given the wizards tend to use DeploymentType; I wonder if each DeploymentType could have an optional filter file associated with it; then we add a DeploymentType of OSIO - then we can keep a list of stuff to filter on on a per deployment basis in the catalog git repo and avoid lots of branching/forking?
The text was updated successfully, but these errors were encountered:
there's a number of boosters that don't work on OSIO right now; rather than making a branch and forking the whole catalog and deleting stuff, I'm wondering if some kinda filter file with patterns for including/excluding missions/runtimes/boosters to filter out might be the simplest approach to filtering stuff out?
i.e. to avoid loads of git issues as we try do keep doing PRs against different branches/forks for boosters that may be excluded for, say, OSIO but not for, say, on premise OSCP or OSD.
Given the wizards tend to use DeploymentType; I wonder if each DeploymentType could have an optional filter file associated with it; then we add a DeploymentType of OSIO - then we can keep a list of stuff to filter on on a per deployment basis in the catalog git repo and avoid lots of branching/forking?
The text was updated successfully, but these errors were encountered: