Instead of using two different modules to generate UUIDs and GUIDs, use
a single implementation, which we use uniformly in all of our codebase,
so that we can drop this from our dependency tree.
Switch to use the new API, which simplifies the code.
Change-Id: I37013c063f283cd27b8ffc48129b35288ce733a5
support loading the full CDR graph, featuring all relations:
-cdr_groups
-cdr_tags
-cdr_mos
-cdr_status
-cdr_relations
-cdr_presentity
-cdr_cash_balances
-cdr_time_balances
aside various fixes, NGCP::BulkProcessor::Closure is introduced,
which provides uniform code execution:
-perl code (from YAML)
-perl code (from string)
-javascript (from string)
an identical symbol table is exposed to either
language env, including the SQL connector api.
Change-Id: If10422df33d996fb6a6a6b53d0ead28ea1cef755
if a table to process has 0 records, this caused stop with an
error. this is ok if running a single task only, but if
mor task are provided, subsequent task will be skipped.
Change-Id: I03b312aa815bfc8b75bf5b058313d8b5de0ab205
the "soap" sql user has no access to the "ngcp" database.
switch to "billing" as a default db to prevent an error when
loading credentials purely from constants.yml
Change-Id: Ia6afd27995784af52ac9beb7ba0d93b353d482d2
huge sqlite databases cause huge tempfiles
(even for SELECT), sometimes too big for
the system's tempfolder.
Change-Id: I7d19b1b30f90d63fdfd41f4c9329708f1584bfc9
to prevent specifying db connections and (unencrypted)
credentials in the config.cfg file, we now support loading
it from constants.yml.
this can be enabled by specifying a path to constants.yml
in config.cfg, ie.
constants_yml = /etc/ngcp-config/constants.yml
particular values can be overloaded, and the order of
precedence is as follows:
1. values in config.cfg
2. values in constants.yml
3. values in provisioning.conf
...
Change-Id: Icc0a57f13e265c3d10bcb697c998e65f2bd6b31d
config options for .csv exports have to be exposable
in bulk-processor .cfg files, ie.
eol
sep_char
quote_char
escape_char
Change-Id: I805f11cc4d11f626bb74638680db4804488f1555
to authenticate (trusted) backend application via EWS, it boils
down to have 3 credential parameters:
tenant_id
client_id
client_secret
Change-Id: I0f42f2e48471ef2c027b6b902123fa7ccf03f1bb
AttachmentDownloader is an abstract base class for mail
services, implemented f.ex. for IMAP protocol.
This commit adds an implementation using the EWS Soap
protocol. It is the final part of the OAuth2 PoC.
Change-Id: Ibb1d115570b2ccd0891cfdc51b53266d6b55e923
EWS::Client::Role::SOAP reimplementation using
LWP::Authen::OAuth2 to support authenticating
backend apps with registered app id.
Change-Id: I607d4a3aa744e39aff27ba3dbc93e9a3a272ca4b
EWS::Client implementation overload to register
the role EWS::Client::Role::GetAttachment providing
the EWS SOAP "GetAttachment" implementation.
Change-Id: Iff3de2fd5626da94e227eabcfe2c9bdfd1d43501
This switches the output to the traditional SI binary unit suffixes, and
to the decimal metric system unit suffixes.
Change-Id: Icf3b6a0c074ad89014884eed3a9643085ee802cf
Change the function to handle bytes by default, which is what most
callers are passing. Add support for terabytes and petabytes. Switch
kbytes2gigs() to be a wrapper over humanize_bytes() for backwards
compatibility for now until all callers are switched. Remove
unnecessary int() coercion from call sites.
Change-Id: I94be536d73930a453d588e0edbb8192d6844bbe0
this tool provides loading and updating the ngcp LNP
database from customer-specific textfiles with many
GBytes and tens of mio. of rows. in a *fast* way.
Change-Id: Ie64b1a9c7dfe3251c41dd443ed937cf8da18cb36