You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 12, 2019. It is now read-only.
I've left the AWS Provisioner state method in place, but it's deprecated. It really needs to be deleted because it causes a decent amount of overhead and adds a lot of complexity to the provisioner.
The ec2-managerapi is now the best sort of information about instance details.
We should use the GET /v1/worker-types/:workerType/stats method to determine instance counts and capacity, the GET /v1/worker-types/:workerType/state to get detailed information about the EC2 resources.
We should expose the DELETE /region/:region/instance/:instanceId and DELETE /region/:region/spot-instance-request/:requestId methods to delete specific instances in the EC2 resource table if the user has the correct ec2-manager:manage-instances:<region>:<instanceId> or ec2-manager:manage-spot-requests:<region>:<requestId> scope.
We should expose the DELETE /worker-types/:workerType/resources method to kill all instances of a workertype if the user has the correct ec2-manager:manage-resources:<workerType> scope.
We should create a basic EC2 Manager debugging tools page which exposes the endpoints with a simple click a button, display the response system:
/v1/internal/regions
/v1/internal/spot-requests-to-poll
/v1/internal/db-pool-stats
/v1/internal/all-state
/v1/internal/sqs-stats
/v1/internal/purge-queues (please do not run while testing, it will mess things up in production)
The text was updated successfully, but these errors were encountered:
I've left the AWS Provisioner state method in place, but it's deprecated. It really needs to be deleted because it causes a decent amount of overhead and adds a lot of complexity to the provisioner.
The
ec2-manager
api is now the best sort of information about instance details.We should use the
GET /v1/worker-types/:workerType/stats
method to determine instance counts and capacity, theGET /v1/worker-types/:workerType/state
to get detailed information about the EC2 resources.We should expose the
DELETE /region/:region/instance/:instanceId
andDELETE /region/:region/spot-instance-request/:requestId
methods to delete specific instances in the EC2 resource table if the user has the correctec2-manager:manage-instances:<region>:<instanceId>
orec2-manager:manage-spot-requests:<region>:<requestId>
scope.We should expose the
DELETE /worker-types/:workerType/resources
method to kill all instances of a workertype if the user has the correctec2-manager:manage-resources:<workerType>
scope.We should create a basic EC2 Manager debugging tools page which exposes the endpoints with a simple click a button, display the response system:
/v1/internal/regions
/v1/internal/spot-requests-to-poll
/v1/internal/db-pool-stats
/v1/internal/all-state
/v1/internal/sqs-stats
/v1/internal/purge-queues
(please do not run while testing, it will mess things up in production)The text was updated successfully, but these errors were encountered: