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

CLI Tools: DBCONTEXT environment variable #927

Closed
bricelam opened this issue Oct 21, 2014 · 1 comment
Closed

CLI Tools: DBCONTEXT environment variable #927

bricelam opened this issue Oct 21, 2014 · 1 comment
Assignees
@bricelam
Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. good first issue This issue should be relatively straightforward to fix. help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. type-enhancement

Comments

@bricelam
Copy link
Contributor

Since the command line interfaces (k ef and ef.exe) don't have a good way of implementing the Use-DbContext command, we should allow an environment variable to be set instead.
@rowanmiller rowanmiller added this to the Backlog milestone Oct 22, 2014
@bricelam bricelam self-assigned this Mar 10, 2015
@bricelam bricelam added the help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. label May 15, 2015
@bricelam bricelam removed their assignment Sep 4, 2015
@bricelam bricelam modified the milestones: 2.0.0, Backlog Jan 13, 2017
@bricelam bricelam self-assigned this Jan 13, 2017
@bricelam bricelam added the tools label Jan 13, 2017
@bricelam bricelam changed the title Commands: DBCONTEXT environment variable Tools: DBCONTEXT environment variable Feb 27, 2017
@bricelam bricelam changed the title Tools: DBCONTEXT environment variable CLI Tools: DBCONTEXT environment variable Feb 27, 2017
@bricelam bricelam mentioned this issue Mar 14, 2017
Closed
@bricelam bricelam modified the milestones: Backlog, 2.0.0 Mar 14, 2017
@bricelam bricelam removed the tools label Apr 26, 2017
@ajcvickers
Copy link
Contributor

Closing as we haven't seen significant demand for this feature. We could revisit this decision based on feedback and we would also consider a well-written community PR for it.

@ajcvickers ajcvickers added closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. and removed propose-close labels Feb 17, 2018
@ajcvickers ajcvickers removed this from the Backlog milestone Feb 17, 2018
@bricelam bricelam added the good first issue This issue should be relatively straightforward to fix. label May 31, 2019
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bricelam bricelam

Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. good first issue This issue should be relatively straightforward to fix. help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. type-enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bricelam @ajcvickers @rowanmiller @AndriySvyryd