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

Registering a polling Tentacle in Tentacle Manager replaces existing tentacle with same name #4362

Closed
tw17 opened this issue Mar 8, 2018 · 1 comment

Comments

@tw17
Copy link

commented Mar 8, 2018

Issue

When registering a polling Tentacle in tentacle manager, it is silently using the --force command which results in any existing tentacles with the same name being overridden in octopus without prompting or notifying the user.

Solution

We should add a "Force (Allow overwriting of existing machines)" check-box to the registration screen for the polling tentacle in Tentacle Manager which would be unchecked by default.

@tw17 tw17 added the area/execution label Mar 8, 2018
@droyad droyad added the size/tiny label Oct 9, 2018
@tw17 tw17 modified the milestone: 2019.1.0 Feb 22, 2019
@tw17 tw17 closed this Feb 22, 2019
@tw17 tw17 self-assigned this Feb 22, 2019
@octoreleasebot octoreleasebot removed this from the 2019.1.0 milestone Feb 22, 2019
@tw17 tw17 added this to the 2019.1.0 milestone Feb 22, 2019
@lock

This comment has been minimized.

Copy link

commented May 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators May 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants
You can’t perform that action at this time.