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

Support environments or config for common args in CLI #700

Closed
k82cn opened this issue Feb 10, 2020 · 3 comments
Closed

Support environments or config for common args in CLI #700

k82cn opened this issue Feb 10, 2020 · 3 comments
Labels
area/cli kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.0

Comments

@k82cn
Copy link
Member

k82cn commented Feb 10, 2020

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature
/area cli
/priority important-soon

Description:

Currently, we support several common arguments for command lines, e.g. --scheduler-name, --master. It's better to have a way to avoid adding those common arguments every-time.
@volcano-sh-bot volcano-sh-bot added kind/feature Categorizes issue or PR as related to a new feature. area/cli priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 10, 2020
@k82cn k82cn added this to the v0.4 milestone Feb 10, 2020
@k82cn
Copy link
Member Author

k82cn commented Feb 10, 2020

/cc @thandayuthapani , please also help on this one when you have time :)

This was referenced Feb 18, 2020
Merged
Merged
This was referenced Mar 3, 2020
Merged
Closed
@k82cn k82cn modified the milestones: v0.4, v1.0 Jun 15, 2020
@stale
Copy link

stale bot commented Sep 13, 2020

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 13, 2020
@stale
Copy link

stale bot commented Nov 12, 2020

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/cli kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
2 participants
@k82cn @volcano-sh-bot