inletsctl icon indicating copy to clipboard operation
inletsctl copied to clipboard

Enable delete via IP address

Open alexellis opened this issue 6 years ago • 6 comments

Expected Behaviour

After provisioning and coming back later, an inlets exit-node will be known mainly by its IP rather than the internal ID used by the cloud provider.

We could do something like this for a friendlier experience:

inlets delete --ip 209.97.131.180

Current Behaviour

We delete via an ID

inlets delete --id 164857028

Possible Solution

if --ip is given, iterate and page through the instances the cloud provider has (filtered by tag?) and match on IP, then use that ID to run the deletion.

This is a follow-on feature from #1

alexellis avatar Oct 29 '19 16:10 alexellis

Removing incorrect label of "bug"

alexellis avatar Nov 11 '19 18:11 alexellis

@alexellis , I will do this one as well.

adamjohnson01 avatar Jan 01 '20 13:01 adamjohnson01

Thanks :+1:

This is going to be rather more involved I think, but would be awesome to have.

In the meantime, can you also send a PR to update the create command so that it prints the sample delete command?

alexellis avatar Jan 01 '20 16:01 alexellis

In the meantime, can you also send a PR to update the create command so that it prints the sample delete command?

Sure, will do!

adamjohnson01 avatar Jan 01 '20 16:01 adamjohnson01

@alexellis, as part of #21 I created a method for each provisioner called List. We could potentially create a new cmd called list that will list all of the exit nodes for the specified provisioner. Let me know what you think.

adamjohnson01 avatar Jan 04 '20 00:01 adamjohnson01

@alexellis , this can be closed as well.

adamjohnson01 avatar Jan 26 '20 14:01 adamjohnson01