-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dns/ddclient - add "get" protocol in custom service type #3523
Conversation
7be7f18
to
8fedac4
Compare
8fedac4
to
c9c4f8d
Compare
dns/ddclient/src/opnsense/mvc/app/models/OPNsense/DynDNS/DynDNS.xml
Outdated
Show resolved
Hide resolved
|
@DaCookie4u thanks, at first glance this looks good. @AdSchellevis will let you know about cleanups in a bit. He also mentioned we could add PUT as well while at it. Cheers, |
dns/ddclient/src/opnsense/mvc/app/models/OPNsense/DynDNS/DynDNS.xml
Outdated
Show resolved
Hide resolved
dns/ddclient/src/opnsense/mvc/app/models/OPNsense/DynDNS/DynDNS.php
Outdated
Show resolved
Hide resolved
dns/ddclient/src/opnsense/scripts/ddclient/lib/account/dyndns2.py
Outdated
Show resolved
Hide resolved
dns/ddclient/src/opnsense/mvc/app/models/OPNsense/DynDNS/DynDNS.php
Outdated
Show resolved
Hide resolved
dns/ddclient/src/opnsense/mvc/app/models/OPNsense/DynDNS/DynDNS.php
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, LGTM
|
I liked the PUT idea, so I put it in. Hope that was OK. I also switched the getattr() method to the general request method. I have the feeling that is cleaner and somehow safer. |
|
BTW, how long does it for plugins to be packaged to the main repository after being committed to master? I couldn't find any info on the exact process that leads from master to package. |
|
master branch merges land in the next development version of the upcoming release. If we can wrap up tomorrow that would be 23.7.2 for early next week. But I think these changes are simple enough to be pushed to stable as well so they will be released directly in 23.7.2. |
Fixed merging the wrong lines.
|
@DaCookie4u looks good, thanks! |
I am loving this new "custom POST" option, but my provider unfortunately only supports GET-requests. POST-requests fail with a CSRF validation.
Since I am unable to change the code on my providers side I decided to implemented a "custom GET" option. This does the same work only with a GET-request instead of POST.
I tried to keep the changes as small as possible. Not sure if that is wanted, but this way 99% of the current code is used and only the request-type changes.