Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

Distinguish between staging & prod when sending data refresh slack updates #473

Closed
1 task done
AetherUnbound opened this issue Jan 19, 2022 · 0 comments · Fixed by #477
Closed
1 task done

Distinguish between staging & prod when sending data refresh slack updates #473

AetherUnbound opened this issue Jan 19, 2022 · 0 comments · Fixed by #477
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🐍 tech: python Requires familiarity with Python

Comments

@AetherUnbound
Copy link
Contributor

Problem

It's not easy to tell based on the slack messages produced by the ingestion server whether a given ingestion is being run in production or staging.

Description

We should pre-pend the messages (or change the bot's name) based on which environment the data refresh is running in.

Alternatives

We could turn off messages altogether for staging (how it is currently) but that would make it harder for us to know when a staging data refresh is complete.

Additional context

Implementation

  • 🙋 I would be interested in implementing this feature.
@AetherUnbound AetherUnbound added 🟨 priority: medium Not blocking but should be addressed soon ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository 🐍 tech: python Requires familiarity with Python labels Jan 19, 2022
@AetherUnbound AetherUnbound self-assigned this Jan 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🐍 tech: python Requires familiarity with Python
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant