mirror of
https://github.com/Unleash/unleash.git
synced 2024-12-22 19:07:54 +01:00
521cc24a22
https://linear.app/unleash/issue/2-1253/add-support-for-more-events-in-the-slack-app-integration Adds support for a lot more events in our integrations. Here is how the full list looks like: - ADDON_CONFIG_CREATED - ADDON_CONFIG_DELETED - ADDON_CONFIG_UPDATED - API_TOKEN_CREATED - API_TOKEN_DELETED - CHANGE_ADDED - CHANGE_DISCARDED - CHANGE_EDITED - CHANGE_REQUEST_APPLIED - CHANGE_REQUEST_APPROVAL_ADDED - CHANGE_REQUEST_APPROVED - CHANGE_REQUEST_CANCELLED - CHANGE_REQUEST_CREATED - CHANGE_REQUEST_DISCARDED - CHANGE_REQUEST_REJECTED - CHANGE_REQUEST_SENT_TO_REVIEW - CONTEXT_FIELD_CREATED - CONTEXT_FIELD_DELETED - CONTEXT_FIELD_UPDATED - FEATURE_ARCHIVED - FEATURE_CREATED - FEATURE_DELETED - FEATURE_ENVIRONMENT_DISABLED - FEATURE_ENVIRONMENT_ENABLED - FEATURE_ENVIRONMENT_VARIANTS_UPDATED - FEATURE_METADATA_UPDATED - FEATURE_POTENTIALLY_STALE_ON - FEATURE_PROJECT_CHANGE - FEATURE_REVIVED - FEATURE_STALE_OFF - FEATURE_STALE_ON - FEATURE_STRATEGY_ADD - FEATURE_STRATEGY_REMOVE - FEATURE_STRATEGY_UPDATE - FEATURE_TAGGED - FEATURE_UNTAGGED - GROUP_CREATED - GROUP_DELETED - GROUP_UPDATED - PROJECT_CREATED - PROJECT_DELETED - SEGMENT_CREATED - SEGMENT_DELETED - SEGMENT_UPDATED - SERVICE_ACCOUNT_CREATED - SERVICE_ACCOUNT_DELETED - SERVICE_ACCOUNT_UPDATED - USER_CREATED - USER_DELETED - USER_UPDATED I added the events that I thought were relevant based on my own discretion. Know of any event we should add? Let me know and I'll add it 🙂 For now I only added these events to the new Slack App integration, but we can add them to the other integrations as well since they are now supported. The event formatter was refactored and changed quite a bit in order to make it easier to maintain and add new events in the future. As a result, events are now posted with different text. Do we consider this a breaking change? If so, I can keep the old event formatter around, create a new one and only use it for the new Slack App integration. I noticed we don't have good 404 behaviors in the UI for things that are deleted in the meantime, that's why I avoided some links to specific resources (like feature strategies, integration configurations, etc), but we could add them later if we improve this. This PR also tries to add some consistency to the the way we log events. |
||
|---|---|---|
| .. | ||
| api/legacy/unleash | ||
| deploy | ||
| integrations | ||
| sdks | ||
| activation-strategies.md | ||
| api-tokens-and-client-keys.mdx | ||
| archived-toggles.md | ||
| change-requests.md | ||
| custom-activation-strategies.md | ||
| environments.md | ||
| event-log.md | ||
| event-types.mdx | ||
| feature-flag-naming-patterns.mdx | ||
| feature-toggle-types.md | ||
| feature-toggle-variants.md | ||
| feature-toggles.mdx | ||
| front-end-api.md | ||
| impression-data.md | ||
| login-history.md | ||
| maintenance-mode.mdx | ||
| network-view.mdx | ||
| notifications.md | ||
| playground.mdx | ||
| project-collaboration-mode.md | ||
| projects.md | ||
| public-signup.mdx | ||
| rbac.md | ||
| segments.mdx | ||
| service-accounts.md | ||
| sso.md | ||
| stickiness.md | ||
| strategy-constraints.md | ||
| strategy-variants.md | ||
| tags.md | ||
| technical-debt.md | ||
| unleash-context.md | ||
| whats-new-v4.md | ||