[FEAT] [Peer] definition within generated wg0.conf should be templated #335
Comments
|
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I am unsure what else I can do to keep this feature request alive. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I've got the same usecase and I completely agree. I'll try to solve this in a fork and maybe submit a PR. |
|
@greigm I've had lots of success using the fork so far. You can pull the image from the link in the PR. You'll just need to regenerate your |
|
Amazing, thanks so much @nonk123. I'll grab it now. |
|
Yep - works like a charm. Nice work! Thanks. |
|
You're welcome! Thanks for giving me a push to implement this too. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is this a new feature request?
Wanted change
I use a grafana dashboard which relies on an exporter which in turn looks for # friendly_name=${PEER_ID} to export meaningful peer names to grafana. It would be nice if the [Peer] definitions inside wg0.conf were templatable in the same way that the [Interface] part is, and each Peer config is. Perhaps this is already possible, but from my initial (poor) reading of the code and the docs, it doesn't seem to be.
Reason for change
Extra flexible configuration. Compatibility with other software.
Proposed code change
No response
The text was updated successfully, but these errors were encountered: