Repository navigation
Replies: 2 comments 1 reply
1 reply
|
You do not need to edit curl -fsS -u USER:PASS http://SOURCE/control/dns_info -o dns-config.json
curl -fsS -u USER:PASS \
-H 'Content-Type: application/json' \
--data-binary @dns-config.json \
http://TARGET/control/dns_configTest this against instances running the same AGH version and keep a copy of each target's configuration first. Clients, filters, rewrites, DHCP, TLS, and statistics use separate endpoints, so a synchronization script should call only the resources you intend to mirror rather than overwrite the whole YAML file. The supported request bodies and endpoints are defined in the repository's OpenAPI specification, including Basic authentication. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Is it there a way to handle the configurations via command line? To automatize or replicate/scale specific action on multiple instances? In my case I have it on a remote machine, on a local machine and on a VM as last resource. Keep them aligned with settings is quite boring, and if I keep slight different configs, the most "easy" thing is to take screenshots of configs to be able to replicate if for any reason I have to reinstall.
At the moment the only solution I see is to manually (or via regexp/sed) edit the configuration files but, as usual, it is risky (the software has updated the file, moved configuration to a different sections, etc etc...).
Is it there a way to not use only the web interface?
All reactions