Description
At this moment, many provisioners have some specific, hard-coded references to inlets. Like tags or firewall rules.
Referring to this repository: https://github.com/inlets/provision-cloudinit-go, removing those references and making the provisioners more generic, they can be used as a library by others.
Expected Behaviour
Most provisioners create cloud host with hard-coded inlets references, like tags.
Current Behaviour
The provisioners can be used by others without creating inlets tags.
Possible Solution
Pass the inlets references to the provisioners as arguments. I'm aware this can be a tedious task, as there are many provisioners and they all have a target cloud specific implementation.
Steps to Reproduce (for bugs)
N/A
Context
Playing around with the provisioners as a library, I've noticed that the cloud hosts are tagged with "inlets"., while I was creating other, non-inlets relared hosts.
Your Environment
- inlets version
inlets --version
N/A - Docker/Kubernetes version
docker version/kubectl version:
N/A - Operating System and version (e.g. Linux, Windows, MacOS):
N/A - Link to your project or a code example to reproduce issue:
https://github.com/inlets/provision-cloudinit-go
Activity