Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Configuration file on network share (homedrive) #8112

Closed
ThiloL opened this issue Oct 30, 2020 · 2 comments
Closed

Configuration file on network share (homedrive) #8112

ThiloL opened this issue Oct 30, 2020 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ThiloL
Copy link

ThiloL commented Oct 30, 2020

Description of the new feature/enhancement

Please add the ability to put the settings.json file to a network share (maybe homedrive) to use the same file from different workstations

Proposed technical implementation details (optional)

You could add a command line parameter to set the configuration file path (i. e. network share/unc path).
@ThiloL ThiloL added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 30, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 30, 2020
@zadjii-msft
Copy link
Member

Thanks for the suggestion! I think largely, this is a duplicate of the discussion we're having in #2303. Or, at least, that's the issue that we've been using for tracking "I want to specify another file to read settings from".

/dup #2303

@ghost
Copy link

ghost commented Oct 30, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Oct 30, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 30, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ThiloL @zadjii-msft