-
Notifications
You must be signed in to change notification settings - Fork 62
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
Enable delete via IP address #2
Comments
Removing incorrect label of "bug" |
@alexellis , I will do this one as well. |
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? |
Sure, will do! |
@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. |
@alexellis , this can be closed as well. |
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:
Current Behaviour
We delete via an ID
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
The text was updated successfully, but these errors were encountered: