New function del_pair() is a copy of del() but it does not delete call counters
on db central. Useful if we want to clean pair db without changing db central.
Change-Id: I936bbb99ce9d5698273d8f72e0f032358bd341cd
(cherry picked from commit d9e55ae48c9fc86af88194dafebf9e236e24c14b)
We were using a mix of .new() and :new() and
that lead us to errors when calling new with parameters
Just be consistent and choose one
Change-Id: Icc2078efb377b80942b2fb518db52df339ecda6a
Unify redis interaction in a class
* allow passing partial config via new()
config will be merged using defined defaults so
missing keys will be appended using values from defaults
Change-Id: I486637e99e0e36fbe1f5a06c703c6b7d2fa77d77
The new function behaves like NGCPDlgCounters:is_in_set but
it uses a regex match to see if the key is contained in the list
Additionally added the helper function 'contains_regex' in the
utils.lua
* ignore vscode files
Change-Id: Iee89f5298ced10c2a9cdf7ebc19a4c0945b8cc9d
We are going to use both modules app_lua and app_lua_sr until we
solve the missing pieces on KEMI:
* KSR.pvx.xavp_get() returns a string like '<<xavp:%p>>' not a table like
sr.xavp.get()
* KEMI lacks of something like sr.xavp.get_keys() funtion
So, migrate everything that we can to KEMI and keep using sr approach
for just that two cases
- mocks/sr.lua: use same objects for same behaviour
Change-Id: I475ff8f820586cdc94c75bff7466238215e05673
The count argument influences the operation in the following ways:
* count > 0: Remove elements equal to value moving from head to tail.
* count < 0: Remove elements equal to value moving from tail to head.
* count = 0: Remove all elements equal to value.
Change-Id: Ia77b760fcada0027fe58a48f4b335d5c264e8917
if true it will check for duplication of keys at the list of counters used
when calling set(). Added is_in_set() to check if a key is already there
Change-Id: Ib1da91dd3cdb13c537577d8e36c1a22920112ce0
Alessio Garzi
Victor Seva
Marco Capetta
Andrew Pogrebennyk