chore(deps): bump github.com/slack-go/slack from 0.12.5 to 0.17.3

[dependabot]

Bumps github.com/slack-go/slack from 0.12.5 to 0.17.3.

Release notes

Sourced from github.com/slack-go/slack's releases.

v0.17.3

What's New

• Add IsEmailConfirmed to User by @​nlopes in slack-go/slack#1458

Fixes

• Parse simple string based errors as part of the response by @​nlopes in slack-go/slack#1452 In the previous version we introduced the ability to parse specific errors (more complex ones) but Slack can still send us a string. string is now the fallback type.

Other

• Examples are now using environment variables and command line arguments consistently by @​nlopes in slack-go/slack#1456 Also added a https://github.com/slack-go/slack/blob/HEAD/examples/README.md explaining the patterns that should be used.

Full Changelog: slack-go/slack@v0.17.2...v0.17.3

v0.17.2

Features added

• Add Timezone parameter for the slack TimePickerBlockElement by @​jamesjarvis in slack-go/slack#1448 and slack-go/slack#1449
• Add support for Slack image file objects in the ImageBlockElement by @​superturkey650 in slack-go/slack#1444
• Add ability to add file ids when updating a message by @​nlopes in slack-go/slack#1451
• Add support for the API endpoint /migration.exchange to the library by @​nlopes in slack-go/slack#1453
• Add /apps.connections.open handler to slacktest by @​prologic in slack-go/slack#1447

New Contributors

• @​jamesjarvis made their first contribution in slack-go/slack#1448
• @​prologic made their first contribution in slack-go/slack#1447
• @​superturkey650 made their first contribution in slack-go/slack#1444

Full Changelog: slack-go/slack@v0.17.1...v0.17.2

v0.17.1

This has the potential to be a breaking change if and only if you have been building SlackResponse by hand, which you shouldn't 😬. If you are, my apologies for adding this in a minor version, I thought the likelihood of this to be very very low. See slack-go/slack#1443 for more details.

Features added

• Add channel_unshared event by @​nlopes in slack-go/slack#1437
• Add missing Blocks to UploadFileContextV2 by @​dalyndalton in slack-go/slack#1435 This adds the missing optional dependency for Blocks to the upload file method, allowing users to use rich blocks and buttons during the file upload process.
• Return Errors field in SlackErrorResponse by @​nlopes in slack-go/slack#1443

Detailed list of all of the changes

• chore: add CI test status badge to README by @​nlopes in slack-go/slack#1431
• feat: add channel_unshared event by @​nlopes in slack-go/slack#1437
• chore: add test for section block expand option by @​nlopes in slack-go/slack#1440
• chore: order inner events vars alphabetically by @​nlopes in slack-go/slack#1442
• chore: better events example code by @​nlopes in slack-go/slack#1441
• feat: Add missing Blocks to UploadFileContextV2 by @​dalyndalton in slack-go/slack#1435
• feat: return Errors field in SlackErrorResponse by @​nlopes in slack-go/slack#1443
• doc: add README.md to examples/eventsapi by @​nlopes in slack-go/slack#1445

New Contributors

... (truncated)

Commits

• e29b7e3 fix: parse simple string based errors as part of the response (#1452)
• 13c4aec feat(users): add IsEmailConfirmed to User (#1458)
• 4a2676d feat(users): add IsEmailConfirmed to User
• 6efef11 feat: bring consistency to examples (#1456)
• 36472df chore: add generated README to examples/
• bc1f95f chore: more linting
• dc611a3 fix(examples): quit if unable to send message
• dccc5d8 chore: remove a bunch of global vars
• 369013a chore: better code
• f89cda5 chore: fix lint in team example
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Assignees

The following users could not be added as assignees: stackrox/infra. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

[rhacs-bot]

A single node development cluster (infra-pr-1664) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1664 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f

[tommartensen]

@dependabot rebase