Skip to content

Use ruby command "gem list" for foreman existence test #93

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

Merged
merged 2 commits into from
Jun 21, 2022

Conversation

elalemanyo
Copy link
Contributor

Hi,
I know this does not solve any current problem, but maybe would be better to use the command gem list to check for foreman. This command gives a better output (boolean) and appropriate exit code.

Thanks

Related with /pull/91

@elalemanyo
Copy link
Contributor Author

@MrJoy I know this is something you fixed a few days ago, but maybe this is a good way to improve it, what do you think?
Or is your way better?
Thanks

@MrJoy
Copy link
Contributor

MrJoy commented May 9, 2022

Seems perfectly reasonable to me.

@kevynlebouille
Copy link
Contributor

Hi @elalemanyo ,

Your version output true or false in the console.

Here is my proposal

if ! gem list foreman -i --silent; then

Co-authored-by: Kevyn Lebouille <[email protected]>
@elalemanyo
Copy link
Contributor Author

Hi @elalemanyo ,

Your version output true or false in the console.

Here is my proposal

if ! gem list foreman -i --silent; then

@kevynlebouille I love your proposal, Thanks!

@elalemanyo
Copy link
Contributor Author

@MrJoy do you think we can merge this? 😁

@MrJoy
Copy link
Contributor

MrJoy commented May 20, 2022

I'm not a maintainer, so it's not really for me to say. I can say that the fix works perfectly fine for my use-case and I fully support merging it.

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

Successfully merging this pull request may close these issues.

4 participants