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

Require confirmation to install #6

Open
leixiaoyu opened this issue Aug 31, 2015 · 3 comments
Open

Require confirmation to install #6

leixiaoyu opened this issue Aug 31, 2015 · 3 comments

Comments

@leixiaoyu
Copy link

I tried to use this package to install RabbitMQ to servers. However, even with --confirm switch, I am still seeing confirmation windows pops up and asking for user interaction. I can see from the package it passes '/S' to Chocolatey, but it does not seem to work for me.

Just wanted to know if anyone has the same issue? I am using Chocolatey v0.9.8.33.

@robertlabrie
Copy link
Contributor

This is a UAC prompt?

Your command/powershell prompt is administrative?

I do the testing in chocolatey 9.9.8+ by running
choco -y install rabbitmq on Windows 7 and Server 2012 and don't get any popups.

@leixiaoyu
Copy link
Author

Thanks for your prompt response. Actually the package was successfully installed when I trigger the job from puppet-chocolatey. However, the job still failed due to an error when continue configuring RabbitMQ.

Is that possible to remove the configuration piece from Chocolatey package? Since each user may want to configure queue in a different way. Keeping the config in factory mode in Chocolatey may be a good idea. In my case, I would like to use puppet to further configure RabbitMQ since I can do much more that way. Just a thought.

@robertlabrie
Copy link
Contributor

So my original goal was to maintain feature parity with the original
package (I inherited this one), You can pass it the parameter NOMANAGEMENT
by passing in -params="/NOMANAGEMENT" but that'll still have the service
install and restart. Try that and let me know.

I install it with PowerShell DSC Chocolatey Provider and it doesn't
complain. I'd like to know exactly why Puppet is beefing with it....

On Tue, Sep 1, 2015 at 2:10 PM, leixiaoyu [email protected] wrote:

Thanks for your prompt response. Actually the package was successfully
installed when I trigger the job from puppet-chocolatey. However, the job
still failed due to an error when continue configuring RabbitMQ.

Is that possible to remove the configuration piece from Chocolatey
package? Since each user may want to configure queue in a different way.
Keeping the config in factory mode in Chocolatey may be a good idea. In my
case, I would like to use puppet to further configure RabbitMQ since I can
do much more that way. Just a thought.


Reply to this email directly or view it on GitHub
#6 (comment)
.

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