89luca89/terrible

[IMPROVEMENT] Support for other providers

Open

#88 opened on Jul 4, 2021

View on GitHub
 (0 comments) (0 reactions) (2 assignees)YAML (29 forks)github user discovery
enhancementexperimentalhelp wantedrefactoring

Repository metrics

Stars
 (259 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

We should support other providers like:

To include multiple providers we should think on how we want to specify the provider, for example:

    hypervisor_1:
      ansible_host: remote_kvm_machine.foo.bar
      ansible_user: root
      provider_type: Proxmox

Or something similar, also we should think on how the code generation will behave, for example

roles/terrible/templates/Libvirt
└── ......tf.j2
roles/terrible/templates/Proxmox
└── ......tf.j2
roles/terrible/templates/oVirt
└── ......tf.j2

And use the provider_type as a variable to discover the templates.

Discussion open on how to approach the problem

Contributor guide

Research direction
Discuss how to define a provider type variable in the Ansible inventory and how to structure template directories for each provider (e.g., Libvirt, Proxmox, oVirt). Investigate how to select the appropriate template based on provider type during code generation.
Tech stack
terraform
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30