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.

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

Start shouldn't require local unit file #5

Open
stongo opened this issue Aug 18, 2015 · 2 comments
Open

Start shouldn't require local unit file #5

stongo opened this issue Aug 18, 2015 · 2 comments

Comments

@stongo
Copy link

stongo commented Aug 18, 2015

Forcing the use of fleetctl submit unitFile and fleetctl start unit for the start method is too limiting for my use. For my use case I need to be able to stop/start units without submitting a new unit file.
Would you be cool with a PR to add an option to bypass the submit step?

@lukebond
Copy link
Owner

hey @stongo good idea. i guess it was written on the assumption you wanted to submit and start a unit.

i guess you'd want something that would ultimately just end up calling fleetctl start unit-name and not providing the whole unit file yeah?

@stongo
Copy link
Author

stongo commented Aug 18, 2015

@lukebond that's exactly it, just want to execute fleetctl start unit-name
working on a PR for this now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants