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
I use config contexts extensively and it's easy to have thousands of contexts. Would it make sense to take an AWS S3 kind of approach to visually organizing contexts? Overall it's a flat file structure; but grouping up names with a delimiter '/' and presenting them as directories? It ensures the name of the context remains unique while giving a more user friendly approach to organizing and browsing the contexts themselves.
and within the GUI laying it out as nested folders:
settings -> corporate -> general
settings -> global -> general
settings -> global -> tunnels
Perhaps add the ability to apply changes at a 'directory' level as well rather than selecting all the files. For example; I may want to apply the weight 500 to everything under settings/global while applying a weight of 250 to everything under settings/corporate without having to select a few hundred contexts each time.
EDIT: Disregard this all; I'm caught up on 3.5 and pulling on contexts from Git is perfect.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I use config contexts extensively and it's easy to have thousands of contexts. Would it make sense to take an AWS S3 kind of approach to visually organizing contexts? Overall it's a flat file structure; but grouping up names with a delimiter '/' and presenting them as directories? It ensures the name of the context remains unique while giving a more user friendly approach to organizing and browsing the contexts themselves.
ex:
settings/corporate/general/ntp
settings/global/general/ntp
settings/global/general/ssh
settings/global/tunnels/aws-east
and within the GUI laying it out as nested folders:
settings -> corporate -> general
settings -> global -> general
settings -> global -> tunnels
Perhaps add the ability to apply changes at a 'directory' level as well rather than selecting all the files. For example; I may want to apply the weight 500 to everything under settings/global while applying a weight of 250 to everything under settings/corporate without having to select a few hundred contexts each time.
EDIT: Disregard this all; I'm caught up on 3.5 and pulling on contexts from Git is perfect.
Beta Was this translation helpful? Give feedback.
All reactions