Separate test environments for staging vs. production #69
Labels
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#224 automated dev-ops workflows}
fediversity/fediversity
#483 [month 24] Software release beta version}
fediversity/fediversity
#177 infrastructure automatically deployed using continuous deployment
fediversity/fediversity
#309 port infra to terraform
fediversity/fediversity
Reference: fediversity/fediversity#69
Loading…
Add table
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?
As a contributor, I want to be able to run deployments during development without affecting production.
Test
Given some checkout of the Fediversity code,
When triggering a deployment via the Panel in development mode,
The given configuration is deployed to staging.
Given some deployed version the Panel,
When triggering a deployment,
The given configuration is deployed to production.
Split test environment into staging and productionto Separate test environments for staging vs. production