Deleting the Authorization

[finnp]

Hi,

I have similar problems to https://github.com/rvagg/ghauth/pull/6. Everytime I redo the authorization, I get an error if I already have authorized the application (but haven't saved the credentials ;)).

The problem is that I would have to delete the authorization (https://developer.github.com/v3/oauth_authorizations/#delete-an-authorization), since I actually don't need it after its use.

Therefore I think it would be nice if ghauth would have a delete method, which first deleted the authorization key (with the authorization key itself ..) and then deletes the .config/<>.json.

This might also be useful for applications that want to implement a logout command.

The revoke methods seemingly can not be used, since they need a client_id, which we don't have. This kind of seems like we either have to keep track of the ID of the authorization, which would suck. A possibility to "self-destruct" them would be nice.

I will look into this - but it kind of looks like that there is no nice way other then let the user delete the tokens for themself..

Best, Finn

PS: This is the workflow that I am actually trying to achieve. Maybe I should just write my custom solution for it. Not sure whether that's within the scope of this module.

[ChanochShayner]

Hey @jenswegar :) This warning message is just a warning and does not affect the file tagging. The reason that skip-resource-types is not working here is - the warning is in the praseFile flow before we start to tag the resources and look at the skip-resource-types list.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.