aboutsummaryrefslogtreecommitdiffhomepage
path: root/handlers
diff options
context:
space:
mode:
authorPaul Bonaud <paul.bonaud@fretlink.com>2020-10-12 17:11:48 +0200
committerPaul Bonaud <paul.bonaud@fretlink.com>2020-10-14 10:04:59 +0200
commit86fe1360cfff115b42607de3ed22fd8c0c75ccc0 (patch)
tree1e926825fba4b454765068d8ee7d77efeb14c3ce /handlers
parent2e423637ee780bd273094ad52e49906100724d08 (diff)
downloadansible-kong-app-86fe1360cfff115b42607de3ed22fd8c0c75ccc0.tar.gz
ansible-kong-app-86fe1360cfff115b42607de3ed22fd8c0c75ccc0.tar.zst
ansible-kong-app-86fe1360cfff115b42607de3ed22fd8c0c75ccc0.zip
Use PUT methods instead of manually detecting if new or update
Kong supports resource idempotency by calling the `PUT` method on user creation/update. Kong will decide by itself whether to create or update the resource. It's clearer and less code on our side. However we can only do this on named resources (not possible on Plugins and Routes which are attached to the `service` with an ID).
Diffstat (limited to 'handlers')
0 files changed, 0 insertions, 0 deletions