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

subcommands missing #5

Open
TheMeier opened this issue Jan 20, 2016 · 4 comments
Open

subcommands missing #5

TheMeier opened this issue Jan 20, 2016 · 4 comments

Comments

@TheMeier
Copy link

in order to be a r10k replacement all subcommands should be implemented.

COMMANDS
deploy Puppet dynamic environment deployment
help show help
puppetfile Perform operations on a Puppetfile
version Print the version of r10k

@alex-harvey-z3q
Copy link

At the very least, there should be syntactic equivalence.

Most basic usage:

r10k puppetfile install 

becomes

g10k -puppetfile

@maxadamo
Copy link

maxadamo commented Feb 8, 2018

Dear Andreas,
I want to connect a question to this ticket (to avoid polluting your repo with too many issues).
Do you think it is beyond the scope of the tool to create switch names, which are compatible with r10k?
Why am I asking this?
It's not a functionality that I personally need, but following up a question that I have read in the puppetcommunity slack channel, some people is wondering if g10k can be used by Code Manager (from puppet Enterprise).
I don't even know if that would be the only problem. I also don't know if it's more convenient to create a wrapper rather than adding unnecessary complexity to the code.

@alex-harvey-z3q
Copy link

alex-harvey-z3q commented Feb 8, 2018

Yeah lack of syntactic equivalence is a shame because if we had it then anyone could just insert a line in their code somewhere:

alias r10k=/usr/local/bin/g10k

Then this would truly become a drop-in replacement.

I am sure the small user base of g10k would understand if a breaking change was made to migrate to use r10k's switch names.

@xorpaul
Copy link
Owner

xorpaul commented Feb 9, 2018

I'll have to think about it.

To be honest the only reason the g10k parameters look the way they do is because of the flag go library.

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

4 participants