Deployed services are accessible #76
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#99 applications deployed on command
fediversity/fediversity
#158 users can update their deployment configurations
fediversity/fediversity
#1059 deployment state stored in state back-end
fediversity/fediversity
#107 Users can configure their desired domains in the online panel, so that the deployed services are assigned the desired domains
fediversity/fediversity
#286 allow accessing test vms from fedi201
fediversity/fediversity
#1326 dedicated DNS environment
fediversity/fediversity
#1451 external DNS accessible for deploys
fediversity/fediversity
Reference
fediversity/fediversity#76
Loading…
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 Fediversity user,
I want to deploy my initial specified configuration on the hosting provider's VMs,
so that I may use my selected applications.
Test:
Given I have a configuration in the FediPanel, but no deployment yet, and DNS is already configured,
When I run the deployment
Then, all configured services are accessible under the specified domain.
I removed all the dependencies since they're not actually blocking this user story. All this one here says is that a deployment can be run and takes effect.
This seems to be blocked by #69 because triggering NixOps from the Panel in a development environment will deploy to our only environment.
kiara referenced this issue2025-04-03 16:48:01 +02:00
kiara referenced this issue2025-05-05 19:48:02 +02:00
This is blocked on an integration test verifying that the deployment indeed works.
kiara referenced this issue2025-06-09 19:46:55 +02:00
Deployed services are accessible under the configured domainto Deployed services are accessible