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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: move SLACK_ENABLE_AVATARS from config to feature flag #30274

Merged
merged 7 commits into from
Sep 16, 2024

Conversation

mistercrunch
Copy link
Member

Needed to make SLACK_ENABLE_AVATARS more dynamic @ Preset so it's easy for us to turn this feature on/off and allow us for a progressive rollout.

@github-actions github-actions bot added the api Related to the REST API label Sep 13, 2024
@pull-request-size pull-request-size bot added size/M and removed size/S labels Sep 13, 2024
@mistercrunch mistercrunch marked this pull request as ready for review September 14, 2024 17:33
@dosubot dosubot bot added change:backend Requires changing the backend change:frontend Requires changing the frontend labels Sep 14, 2024
@@ -149,7 +149,14 @@ services:
disable: true

superset-node:
image: node:20
build:
Copy link
Member Author

Choose a reason for hiding this comment

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

bycatch - somehow superset-node wasn't using the proper target, which explains some issues with zstd we've seen before, which gets installed at the os-level here. There's also the "memory snag" script and the DEV_MODE logic to skip the actual webpack build since we run npm run dev on startup.

Copy link
Member Author

Choose a reason for hiding this comment

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

I thought I had caught/fixed that in some other PR, but guessing it got lost in the shuffle.

Copy link
Member

Choose a reason for hiding this comment

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

Nice, thanks for fixing that

Copy link
Member

@rusackas rusackas left a comment

Choose a reason for hiding this comment

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

Please make sure it gets an entry in FEATURE_FLAGS.md as well :)

Pinging @eschutho for review since she's been handling most of the Slack integration scope.

Also, this might bring up the age-old debate of config vs. feature flags. I'm OK with Feature Flags for cases like this where platforms (Launch Darkly, Split, etc) can hotwire them as needed. Others, however, feel that Feature Flags should be temporary as a development pattern before being eventually deprecated/removed. Sounds like this one is effectively permanent.

# If on, you'll want to add "https://avatars.slack-edge.com" to the list of allowed
# domains in your TALISMAN_CONFIG
SLACK_ENABLE_AVATARS = False

Copy link
Member

Choose a reason for hiding this comment

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

Since this hasn't been released in an official version, I think this breaking change is ok.

Copy link
Member Author

Choose a reason for hiding this comment

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

Right, and I added a note in UPDATING.md as a heads-up

Needed to make SLACK_ENABLE_AVATARS more dynamic @ Preset so it's easy for us to turn this feature on/off and allow for a progressive rollout.
Copy link
Member

@rusackas rusackas left a comment

Choose a reason for hiding this comment

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

Thanks!!!!

@mistercrunch mistercrunch merged commit f315a4f into master Sep 16, 2024
34 checks passed
@mistercrunch mistercrunch deleted the ff_slack branch September 16, 2024 23:07
@sadpandajoe sadpandajoe added the v4.1 Label added by the release manager to track PRs to be included in the 4.1 branch label Sep 16, 2024
sadpandajoe pushed a commit that referenced this pull request Sep 16, 2024
@github-actions github-actions bot added 🍒 4.1.0 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels labels Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Related to the REST API 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels change:backend Requires changing the backend change:frontend Requires changing the frontend packages size/M v4.1 Label added by the release manager to track PRs to be included in the 4.1 branch 🍒 4.1.0 🍒 4.1.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants