Skip to content

Review Current VRMS Slackbot Implementation #16

New issue
New issue
Closed
Closed
Review Current VRMS Slackbot Implementation#16
Labels
complexity: mediumfeature: slackbotrole: DevOps Engineeraka Infrastructure Engineersize: 1ptCan be done in 4-6 hours
Milestone
06.02 Infrastructure - Org - Should have

Description

@Neecolaa
Neecolaa
opened on Feb 24, 2022

Overview

We need to do a deep dive on the existing VRMS slackbot.

Action Items

  • Create a list of files changed during slackbot PRs (add to Resources/Instructions)
  • Look through current code to figure out what it's doing
  • Contact VRMS team for information

Resources/Instructions

Closed pull requests related to slackbot: https://github.com/hackforla/VRMS/pulls?q=is%3Apr+slackbot+is%3Aclosed+

Activity

  1. JasonEb
    added
    role: missing
    size: missing
    feature: missing
    on Apr 3, 2022
  2. ExperimentsInHonesty
    added
    size: 1ptCan be done in 4-6 hours
    role: Data Engineer
    role: DevOps Engineeraka Infrastructure Engineer
    feature: slackbot
    and removed
    role: missing
    size: missing
    role: Data Engineer
    feature: missing
    on Jun 12, 2022
  3. ExperimentsInHonesty
    modified the milestones: 05 Infrastructure Must Haves, 05 Infrastructure Uncategorized, 05.02 Infrastructure Should have on Jun 12, 2022

  4. fyliu commented on Jun 13, 2022

    @fyliu
    fyliu
    on Jun 13, 2022
    Member

    Looks like I should have commented on this issue rather than the other one. See that issue for reference.

    The quick summary

    1. I went to some VRMS meetings and learned that they are no longer using their old slackbot that this issue is interested in.
    2. The person who wrote it is also no longer with the project.
    3. I did review the current code and it's not being called anymore. What it did was use the bot to send messages to slack users using their IDs. It's not actually using the slack app, but was calling the slack API from software.
    4. During a later VRMS meeting, there was someone, Tim Shaker, who was working on a new slack app. It sounded like what we're trying to do in OPS. But if they're doing it in VRMS, there's no point in OPS finding out the implementation and working on another one, since there's only 1 remaining app slot in the free slack tier.

    I think we should close this issue. It's no longer relevant.

  5. JasonEb
    closed this as completedon Sep 18, 2022
  6. ExperimentsInHonesty
    added this to CoP: DevOps: Project Boardon Jun 14, 2024
  7. ExperimentsInHonesty
    moved this to Done in CoP: DevOps: Project Boardon Jun 14, 2024
  8. ExperimentsInHonesty
    added
    complexity: missing
    on May 19, 2025
  9. ale210
    added
    complexity: medium
    and removed
    complexity: missing
    on Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    complexity: mediumfeature: slackbotrole: DevOps Engineeraka Infrastructure Engineersize: 1ptCan be done in 4-6 hours

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions