Repository navigation
Enable delete via IP address #2
Description
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
Activity
alexellis commentedon Nov 11, 2019
Removing incorrect label of "bug"
adamjohnson01 commentedon Jan 1, 2020
@alexellis , I will do this one as well.
alexellis commentedon Jan 1, 2020
Thanks 👍
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?
adamjohnson01 commentedon Jan 1, 2020
Sure, will do!
adamjohnson01 commentedon Jan 4, 2020
@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 commentedon Jan 26, 2020
@alexellis , this can be closed as well.