github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-07 05:09:18 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #449] FR: Automatic DNS provisioning (upon resource creation) #10221

New Issue
Closed
opened 2026-05-06 13:21:41 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-06 13:21:41 -05:00
Owner
Copy Link

Originally created by @achtnullzwei on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/449

Create the ability to automatically provision relevant DNS entries upon creating a resource. Similar to the behavior in CF. Something like this:

  • Object to configure domain, provider & credentials for the domain provider API
  • Upon creating a service, check the domain, if its available in the object
  • if yes, provision the relevant dns entry to the domain via domain provider API
  • upon removal of the resource, remove the dns entry

Of course, this depends on whether the domain provider has a proper API etc. I assume for the more commonly used ones, there are existing libraries that could be leveraged.

Would be a rly nice feature. :)

Originally created by @achtnullzwei on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/449 Create the ability to automatically provision relevant DNS entries upon creating a resource. Similar to the behavior in CF. Something like this: - Object to configure domain, provider & credentials for the domain provider API - Upon creating a service, check the domain, if its available in the object - if yes, provision the relevant dns entry to the domain via domain provider API - upon removal of the resource, remove the dns entry Of course, this depends on whether the domain provider has a proper API etc. I assume for the more commonly used ones, there are existing libraries that could be leveraged. Would be a rly nice feature. :)
GiteaMirror commented 2026-05-06 13:21:42 -05:00
Author
Owner
Copy Link

@achtnullzwei commented on GitHub (Apr 1, 2025):

Seems this was already discussed in #259

I still think it would be a nice feature. Maybe long term :)

<!-- gh-comment-id:2770496217 --> @achtnullzwei commented on GitHub (Apr 1, 2025): Seems this was already discussed in #259 I still think it would be a nice feature. Maybe long term :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#10221
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?