AS a developer, I want the registry to allow me to specify if a command should be registered only on certain environments #38

Closed
opened 2023-09-10 19:32:17 +01:00 by Vylpes · 1 comment
Owner

Epic:
Story Points: 5


AS a developer, I want the registry to allow me to specify if a command should be registered only on certain environments
SO THAT I can have testing-tools available to testers but not to general production users

Acceptance Criteria

AS a developer
GIVEN I create a command I want only to be available on 1 environment
WHEN I register this with the environment's flag
THEN this should only be registered if the environment is the one specified

Subtasks

  • Create environment enum flag
  • Apply environment flag upon bot start
  • Add flag to registry
  • Check flag registry against environment variable

Notes

  • We should make these an enum flag, so production = 1, stage = 2, dev = 4, etc.
Epic: \ Story Points: 5 --- AS a developer, I want the registry to allow me to specify if a command should be registered only on certain environments SO THAT I can have testing-tools available to testers but not to general production users ## Acceptance Criteria AS a developer GIVEN I create a command I want only to be available on 1 environment WHEN I register this with the environment's flag THEN this should only be registered if the environment is the one specified ## Subtasks - [x] Create environment enum flag - [x] Apply environment flag upon bot start - [x] Add flag to registry - [x] Check flag registry against environment variable ## Notes - We should make these an enum flag, so production = 1, stage = 2, dev = 4, etc.
Vylpes added the
type
story
label 2023-09-10 19:32:25 +01:00
Vylpes added this to the 0.2.0 milestone 2023-09-11 20:29:17 +01:00
Vylpes changed title from Add ability to have commands registered only on certain environments to AS a developer, I want the registry to allow me to specify if a command should be registered only on certain environments 2023-09-13 15:28:11 +01:00
Vylpes added this to the 0.2 Sprint 1 project 2023-09-16 15:01:58 +01:00
Vylpes self-assigned this 2023-09-16 15:02:28 +01:00
Vylpes started working 2023-09-29 18:03:30 +01:00
Vylpes stopped working 2023-09-29 18:22:00 +01:00
18 minutes 30 seconds
Vylpes modified the project from 0.2 Sprint 1 to 0.2 Sprint 2 2023-10-07 14:14:00 +01:00
Vylpes added spent time 2023-10-10 17:35:58 +01:00
15 minutes
Member

Passing as this isn't that testable, but will be in future stories

Passing as this isn't that testable, but will be in future stories
VylpesTester added spent time 2023-10-15 16:02:20 +01:00
5 minutes
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Total time spent: 38 minutes 30 seconds
Vylpes
33 minutes 30 seconds
VylpesTester
5 minutes
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: External/card-drop#38
No description provided.