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

[RT-2975] Have mandatory env variables that have no default and must be set by the user #7

Open
blu3r4y opened this issue Aug 31, 2022 · 0 comments
Labels
enhancement New feature or request needs refinement Issues skeletons that are not ready to be taken
Milestone

Comments

@blu3r4y
Copy link
Member

blu3r4y commented Aug 31, 2022

Acceptance Criteria:

  • As a exploit dev, I have an exploit where I need the user to set a certain argument and I can't set a default for it
  • In the UI, show me that a certain env variable must be set by the user
  • Disallow running certain steps if mandatory env variables are not set yet
  • The backend must accept env variables without a "default" key - this indicates a mandatory field
@blu3r4y blu3r4y added enhancement New feature or request needs refinement Issues skeletons that are not ready to be taken labels Aug 31, 2022
@blu3r4y blu3r4y added this to the Later milestone Aug 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request needs refinement Issues skeletons that are not ready to be taken
Projects
None yet
Development

No branches or pull requests

1 participant