Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: GA (remove flag) for Slack App integration #4765

Merged
merged 1 commit into from
Sep 21, 2023

Conversation

nunogois
Copy link
Member

https://linear.app/unleash/issue/2-1405/remove-slackappaddon-feature-flag-and-make-this-ga

GA's the new Slack App integration by removing the feature flag 馃殌

@vercel
Copy link

vercel bot commented Sep 18, 2023

The latest updates on your projects. Learn more about Vercel for Git 鈫楋笌

2 Ignored Deployments
Name Status Preview Updated (UTC)
unleash-docs 猬滐笍 Ignored (Inspect) Sep 18, 2023 2:26pm
unleash-monorepo-frontend 猬滐笍 Ignored (Inspect) Sep 18, 2023 2:26pm

Copy link
Contributor

@gastonfournier gastonfournier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a minor comment maybe, but I'm curious about the change

@@ -9,7 +9,7 @@ export const addonDefinitionSchema = joi.object().keys({
documentationUrl: joi.string().uri({ scheme: [/https?/] }),
description: joi.string().allow(''),
howTo: joi.string().optional().allow(''),
deprecated: joi.boolean().optional().default(false),
deprecated: joi.string().optional().allow(''),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this change needed? Sounds like deprecated should be a boolean. In OpenAPI there's deprecated + deprecatedDescription IIRC

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This fixes and adapts the addon schema to how the deprecated property really works right now: It acts as both the boolean that tells us whether an addon/integration is deprecated and the message why.

This feels pretty clear to me, as you won't specify a deprecation property for non-deprecated addons. But if you feel it's clearer to have 2 separate properties for example:

  • deprecated - Boolean
  • deprecatedDescription - String

I can also do the change.

WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chiming in that I like the approach with two properties - one for a boolean and the other with a description

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't mind either way, it's clear to me if you say deprecated: "reason" that the feature is deprecated (so no need to split).

But I didn't spot anything in the PR that was deprecating something with a string, and therefore these changes seem unrelated to the PR. Also, if unrelated, why are we not getting compilation errors? Maybe because of javascript?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, and because this is the first time we deprecate an addon, this is still greenfield and it's not something we expose. https://docs.getunleash.io/reference/api/unleash/update-addon

Copy link
Contributor

@gastonfournier gastonfournier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@nunogois nunogois merged commit ea9901c into main Sep 21, 2023
11 checks passed
@nunogois nunogois deleted the chore-ga-slack-app-addon branch September 21, 2023 12:56
nunogois added a commit that referenced this pull request Sep 21, 2023
Fixes what this breaks: #4765 -
The Datadog integration needs a `flagResolver`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

3 participants