mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #2429] [feature]: Team specific environment variables #821
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#821
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kiriti-iselect on GitHub (Jun 16, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2429
Originally assigned to: @AndrewBastin on GitHub.
Is there an existing issue for this?
Summary
Please provide team specific environment variables for team collections. Currently, the collections are synced between teams but not the environment variables so basically collection is broken if environment variables doesn't sync.
Currently, environment variables are only for local collection.
Why should this be worked on?
Team collections can't be leveraged to its full capacity unless environments can be synced between team members. Most of time, the collections are dynamic with the use of environment variables.
Example:
Prod stage might have different api endpoint and api key
<<url>>/shortfunnel-health?apiKey=<<apiKey>>where value ofurlwill be/prod/pathDev stage might have different api endpoint and api key
<<url>>/shortfunnel-health?apiKey=<<apiKey>>where value ofurlwill be/dev/pathAlso one may be generated different environment variable using
pre-request-scriptspecific to the state/env@AndrewBastin commented on GitHub (Jun 16, 2022):
We are actually working on this and hope to ship this in the coming weeks!
For the Hoppscotch team:
Internally tracked by hoppscotch/internal-issues#1