- Address an issue at
ConversationOrcherstrator
job which was not taking care abouttoken owner
in kick stage
- Introduce
slack:user:terminator
command which allow you to kick everyone
- Upgrade slackbot for SeAT 3
- Make some improvements on commands so you can either call them with user or group id
- Use the new
user.conversations
endpoint from Slack API on user list in order to show you in which channels an user is
- Address an issue which avoid job status to be updated when an exception occurred from api fetch flow
- Address an issue which avoid sync:user job to be run when other Slack job were running (thanks @herpaderp)
- Address an issue related to log rotation
- The sync user job will now only attempt to sync active SeAT account.
- Jobs are now more verbose about what they are doing
- In order to improve issue fix reactivity, a new logger has been implemented which will forward debug information to Loggly
- Slack API response header are forwarded for all HTTP error (4xx or 5xx)
- Slack API request ID is always sent. It's only usable by Slack support team
- Your SeAT server IP is always sent. It will be usefull for people who goes on SeAT slack #support
- Slack API requested endpoint is always sent. (https://api.slack.com/methods)
- Slack API response body is only sent for HTTP error (4xx or 5xx) and API error
- Installed slackbot version is always sent. It will help to detect issues related to outdated package
- Those information are only visible by SeAT core team and sent to https://warlof.loggly.com
The staff is wishing you an happy new year 2018 !
- Handle an issue related to request amount and 429 HTTP response from Slack service
- Handle an issue which may skip request cool down in specific case
- Improve logability by including request ID, as well as headers and body in debug mode
- Update the user agent which should be more use full for Slack Team
- Automagically rotate log file
- Critical hotfix which is handling an issue related to JobManager who can lead to an fatal error
- Handle an issue which was not returning empty channels list when either user account or keys were disabled
- Handle an issue which was related to syncing process on old coupling. Now, coupling are removed if target user is non longer valid.
- Handle an issue on logging related to query statement when the process kick an user from a channel.
Merry Christmas SeAT ~ Devs :)
- Rewrite the connector in order to be less hammerhead on Slack services
- Paginated result are now also delayed
- Job will now use short life cache in order to reduce call amount in despite of versatility of data
- Small UI improvement at user mapping level
- New commands for a better management :
slack:conversation:sync
,slack:user:sync
,slack:user:invite
,slack:user:kick
- Invite and kick commands can now be used with a SeAT user id as parameter in order to invite or kick specific user
Be sure to publish assets, there are some new style tweaks
Be sure to run migration which will include scheduler update with new commands
- Fixing backward compatibility issues over channels and groups
- Fixing key cache issues
- Recovering unit tests
- Replacing channels/groups API call with new conversation endpoints
- Implementing paginate on API responses
- Code refactoring
- Fix account state check according to SeAT web 2.0.19 breaking change
- Fix an issue related to Slack API policy change for user mail address
- Add a 1 second cool down on Slack Api request according to their limitation
- Code refactorying
- Fix an issue which was preventing disabled account to be monitored by the bot (thanks @herpaderp)
- Fix an issue which was preventing a new instance to be deployed if this package was already present in
composer.json
file
- Fix an issue which was preventing to remove public filter
- Fix an issue which was returning the wrong channel name on public filter
- Add new user:email.read scope which has been added by Slack Team on November 9th.
Warning
If you already had a working bot prior to this date, the update isn't mandatory and you have nothing to do.
If you've setting up a new installation, between November 9th and February 18th, you MUST drop the existing application and create a new one. As soon as the new application has been created, you have to hit the red rubber Button on both
Client ID
andClient Secret
fields into SeAT and fill them with the new credentials. Finally, you can hit theupdate
button which will redirect you to Slack Authentication as a fresh bot install.
- Add a filter for corporation title
- Fix few issues related to Slack implementation (you need to restart supervisor in order change are took in account)
- Improve cachability
Update Slack channels and groups
andUpdate Slack users
commands in settings are now refreshing cache- Slack log is no longer displaying an entry every time the bot is proceeding invitation
- Improve Slack User Mapping with the channels list where an user is in
This new version is compatible with SeAT 2.x. I choose to follow SeAT major version in order to make life easiest for maintainers.
Slack RTM has been replaced by Slack Event API which is easier to set than using a Daemon.
Due to this change, Slackbot is no longer processing Team Invitation. Team invitation is a non official endpoint which is only usable with test token, and Slack Event require official OAuth token.
Warning
You have to create new credentials in
Slackbot Settings
(follow the link bellow credentials fields).
Slackbot namespace has changed for
Warlof\Seat\Slackbot
and Slack credentials are now stored into officialSeat
setting table.
Supervisor configuration related to Slackbot Daemon is non longer required
Redis is now used in order to reduce call amount through Slack REST API.
Handle Team Invitation
exception in logs in order to avoid to barely spam SeAT stats with unrelevant exception.
Introduce a new event kind called "sync" into which those exception are published.
Add a constraint into slack:users:update
command which exclude slackbot
from valid users. It appears that slackbot
is not considered as a bot by Slack API.
We're waiting for a ticket issue response from Slack Team related to this bug.
Add a local channels clear which will delete no longer valid channels to the command slack:channels:update
if there is an issue with the daemon.
remove MPM channels from private channels list
fix log issues which was logging event even when they didn't happen. rename slack command exclude general channel from member list and add general flag to channels
Warning
This update is an upgrade and need a migration. Run
php artisan migrate
command in order to update schemas.
This update replace
slack:update:channels
andslack:update:users
withslack:channels:update
andslack:users:update
respectively.
Due to latest modification, you need to run
slack:channels:update
command in order to update yourslack_channels
flags.
Report any bugs on github.
add test coverage for SlackApi Helper fix Daemon issue related to user and channel creation
fix and refactor slack access creation
fix channels update refactoring issue which avoid new record to be saved
fix API issue for is_bot flag usage which is not available on deleted user as a result, add deleted check
Fix issue for new user invitation
Implement channel_rename and group_rename event into Slack Daemon in order to keep channel table up to date
Add a way to rename channel when user run slack:update:channels
and the channel already exist in SeAT
Fix an issue which was running slack:update:channels
when people clic on "Update Slack users" from
Slackbot Settings UI.
Replace jclg/php-slack-bot
package which avoid to use stable flag and cause some issue,
with ratchet/pawl
and a homemade RTM daemon.
Fix a query issue introduced with version 0.4.0 and public filter
Add a log system which store event history (invite, kick and mail issue) Remove unset mail exception from fail job
Fix manual user sync with job slack:update:users (set invited flag to true)
Add a way to create public filter (grant everybody to be in a channel) Remove eveseat/seat package from dependencies
Fix 0.3.4 typo issue
Update Slack API and add a control to member function is order to check that a channel is not a MP channel Fix javascript on setting view
Version fix
Fix an issue on slack:update:users command which avoid slack user refresh.
Due to a Slack API issue in OAuth mechanism which is used by this extension in order to invite and kick user, the OAuth credentials has been temporarily disabled waiting an answer from Slack support.
In order to provide you a way to keep using the bot, the old connection method has been restored (using testing token).
You need to update the token using the test token and reload supervisor.
Sincere regrets for this perturbation.
In order to keep people inform, the release 0.3.0 provides a way to get live changelog.
This new feature will be used in order to describe last change in the plugin and will be a way to warn people about new release.