-
### OpenTofu Version
```shell
Doesn't matter
```
### The problem in your OpenTofu project
OpenTofu lacks abstractions that allow one to separate the shape of their infrastructure from the concrete…
-
Gravité Code Description Projet Fichier Ligne État de la suppression Détails
Erreur (active) E0304 aucune instance de modèle de fonction "resource_manager::get_resource" ne correspond à la liste d'ar…
-
Segueing from #3, Resources should be accessible by the users who have permission to do so _via any module_. I was thinking that maybe we should create a classification mechanism to allow developers t…
-
Resources on larger nodes are currently defined in an ad-hoc fashion.
Resources on the embedded nodes are based on a trait.
We must define a trait / know abstraction for resources on *nix nodes an…
-
Create a graphics abstraction over Vulkan, to keep the possibility of supporting other APIs open for the future.
~My abstractions will be Vulkan/Khronos flavored, i.e. UniformBuffer in place of Con…
-
Right now, the `resource` abstraction is mixed in with the Rest library, but to my eyes, resources are a protocol-agnostic pattern. If the resource abstraction uses no REST terminology it should be po…
-
It seems strange that resource requests are specified at a task level instead of a executor level where images are actually specified. The lack of flexibility surrounding resource allocation at this l…
-
### What is the problem you're trying to solve
We do have a number of `walkers` abstractions around (for network, images, etc.).
They may have seemed like a good abstraction at the time, but they ar…
-
RI logic right now is in various places throughout the code base. We split and join on `"/"` in a bunch of places. We really should have that and other RI-specific logic in an abstract layer. Could be…
sjrct updated
5 years ago
-
consider an abstraction vs concretion domain split in the model