slack-ruby
Legacy Tokens may no longer be generatable
It seems that new legacy tokens can't be generated any more, as described here.
Am I correctly interpreting this message from [this page]
(https://api.slack.com/legacy/custom-integrations/legacy-tokens#token-mgmt)?
@wasabigeek Are you able to confirm this is also the behavior of your slack account?
I am seeing the same in my test account, which was created sometime last year (I don't think I was able to create it then either), as well as the bot we use at work (which is still on a legacy token, but created a few years ago).
It might be worth bringing this up again, as the CLI requires the use of tokens that can no longer be generated.
It looks like the whole library now has no working examples, at least as far as I can see. This appears to be a dead project.
It looks like the whole library now has no working examples, at least as far as I can see. This appears to be a dead project.
The library is alive and well, but the CLI documentation needs to be updated. The CLI also has a faraday incompatibility that was fixed in #434 and needs to be released (2.1.0) that I can do soon. I believe https://api.slack.com/tutorials/tracks/getting-a-token is the new/current way for getting a token, but I haven't tried - we also could extend samples to require an app token and generate a user token by authorizing a user.
@nello Why don't you help us update the docs?
