AMP icon indicating copy to clipboard operation
AMP copied to clipboard

FR - add disable provisioning on individual target

Open southnode opened this issue 3 years ago • 2 comments

This is not for requesting support for new games/applications

To do this you should go to https://github.com/CubeCoders/AMPTemplates and first attempt to build a configuration yourself - otherwise you can request a template from this repo.

Feature Request

Add ability to disable a target from provisioning via a controller

Feature Information:

Add the ability to designate a target not to be enabled for automated provisioning. For cases of staging, pre-provisioning of untagged targets, or simply sandboxing. The ability to disable (and re-enable) a target to be a valid provisioning node for a controller should be implemented. This would go well in the "edit" section. UI should indicate that a controller is disabled for automated provisioning (such as a grey colourway or contrast).

This should not disable provisioning manually by an admin.

I confirm:

  • [x] that I have searched for an existing feature request matching the description.

southnode avatar Sep 30 '22 14:09 southnode

This seems like a good implementation would be an option to set a target to "Maintenance Mode" which could signify no instance deployment, no allowing instance starts/updates without permission, etc.

What are your thoughts?

IceOfWraith avatar Jul 30 '24 06:07 IceOfWraith

That's effectively it - just disable the ability for users to do anything instance-wise (allow them to start and stop their gameserver, but not affect the instance itself), disable provisioning (set the provisioning weight to 0 or something, or disallow it to be present in the list) but have the underlying services still usable.

A Super-Admin should still be able to perform actions manually however, including provisioning new services on the node, but automated actions such as WHMCS calls should ignore it completely (other than suspending an instance)

Edit: come to think of it, this should only apply to "additive" things. Suspension of instances and termination of instances on a "Maintenance Mode" target should continue to go through as normal. Otherwise you've got a potential for a large cleanup operation.

southnode avatar Jul 30 '24 06:07 southnode