Question - does consul offers http endpoint for kv bulk import? i understand consul cmdline support import from file, but haven’t seen similar feature through http endpoint.
The intention is not to enforce atomicity (but certainly not against it). We are evaluating if there’s efficient way to upload O(10K)~O(100K) kv pairs. It would obviously take too long if we can upload one kv pair at a time…
The binary uses the API http end point as well so that’s not any different.
BTW, if these are “vault” secrets, you cannot import them through consul by-passing vault. You have to use the Vault API to do any of the importing.
One more note, these were secret spread around different paths, ~80 namespaces. Also, this wasn’t all single KV entries, there were cases where 15-18 KVs were being imported into a single secret – that to me is a single operation/secret.
Somehow related, are you familiar with recursive delete and get behavior in consulKV? Do they also operate one-pair-at-a-time under the hood like put? thanks
Another follow up - given our usage pattern, say about 400K kv pairs, and all of them changes roughly O(1) times a day, would this change rate pose performance concern on consul kv store (for instance, defragmentation/etc., nothing specific, just general question)? would be great if there’s best practice reference to consulKV from load/usage pattern perspective. thanks.