Way to use terraform providers with NixOps4 #129
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
#296 orchestrator features
fediversity/fediversity
Reference
fediversity/fediversity#129
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?
As a developer, given I have a Terraform provider implementing an integration I need, I want to be able to use its functionality in NixOps4, such that we would not need to re-implement functionality where such prior art already exists.
Test:
Given I have a TF provider, when I want to use it with NixOps4, I can.
Notes to tackle this:
tofu providers schema -jsonShould this be reported on NixOps4's repo?
@Niols: i'm not sure this would be considered part of the core repo there - tho this ticket came from @roberth, so at least he knows.
What's the criterion to close the issue?
@kiara wrote in Fediversity/Fediversity#129 (comment):
Fair enough, i guess we just want a specific type of provider. Ideally it would go in an issue in the nixops4 org, just not on nixops4/nixops4?
@Niols i'll defer that question to @roberth.
@fricklerhandwerk I updated the ticket a bit, tho it may need further work. I believe @roberth knows better tho.
kiara referenced this issue2025-02-24 14:03:46 +01:00
superseded by #307