ngcp-panel

Commit Graph

Author	SHA1	Message	Date
Kirill Solomko	78b80e7064	TT#149459 enhance expand functionality with allowed_roles * allowed_roles in the expand defintion restrict the field only to the roles in the allowed list, otherwise the field is not expanded. Change-Id: Ib6f776388457327f2fa85e71deb9591022cee2da	5 years ago
Kirill Solomko	8c556bbe36	TT#149459 improve and automate expand functionality * add dictionary support for fields that are expanded if encountered in all endpoints, with a possibility to override it, if defined on the endpoint's field level * move expand definitions from form fields into the Expand dictionary * simplify the expand usage, it now operates only with the <x>_id fields that are returned and visible in the response (e.g. if reseller_id is returned, then ?expand=reseller_id), the returned expand object name is <expand_field_name>_expand the, so in case of ?expand=reseller_id, the returned object will be reseller_id_expand * adapt Role/SystemContacts to work correctly with the expand functionality * expanded fields are returned as <expanded_field_name>_expand Change-Id: I4cab44ede9b40c70a95bbcedc81f58dd1f4e3b67	5 years ago
Rene Krenn	2537819f0d	MT#12643 billing networks and multi bill prof WIP -properly validate billing mapping intervals -api/contracts and api/customers complete +the problem with updating the "prepaid" preference remains at the moment +billing_mappings field contains future (editable) mappings only, the full schedule is given in a separate field +hal-links to all occurring billing profiles and networks -extended tests: api-customer.t and api-contract.t -api-billingnetworks.t test -billing networks panel controller +search by enclosed IP address -panel UIs for billing networks, customers, contracts +past billing mapping intervals that cannot be edited are displayed by a seperate hfh "block" part of the billing_profiles repeatable -profile packages api, UI +terminating billing profiles (MT#8645) will be broken +fixed now: profile cannot be terminated unless there are: -zero non-terminated customers, whose mappings contain the profile with future or open end -zero profile packages, that link to the profile in either one of their initial-, underrun- or topup profile sets +panel edit should work, termination wip +topup_profiles w/o amounts +contracts/customers API profile_package_id field: +apply the package's initial profiles +api/customer and api/contract profile definition modes (id/profiles/package) +api OK, api-customer.t tests +customer and contract panel UI with selector to specify actual billing mapping, schedule or profile package (same as api) +terminate logic harmonized: profiles, networks, packages +api tests updated +prepare for merging: cleanup, enable tests Change-Id: I6c0dec72f490b5731fc673cd393d6aeb08dd8143	11 years ago

Author

SHA1

Message

Date

Kirill Solomko

78b80e7064

TT#149459 enhance expand functionality with allowed_roles

* allowed_roles in the expand defintion restrict the field
  only to the roles in the allowed list, otherwise the field
  is not expanded.

Change-Id: Ib6f776388457327f2fa85e71deb9591022cee2da

Kirill Solomko

8c556bbe36

TT#149459 improve and automate expand functionality

* add dictionary support for fields that are expanded
  if encountered in all endpoints, with a possibility
  to override it, if defined on the endpoint's field
  level
* move expand definitions from form fields into the
  Expand dictionary
* simplify the expand usage, it now operates only with the
  <x>_id fields that are returned and visible in the response
  (e.g. if reseller_id is returned, then ?expand=reseller_id),
  the returned expand object name is <expand_field_name>_expand
  the, so in case of ?expand=reseller_id, the returned object
  will be reseller_id_expand
* adapt Role/SystemContacts to work correctly with the expand
  functionality
* expanded fields are returned as <expanded_field_name>_expand

Change-Id: I4cab44ede9b40c70a95bbcedc81f58dd1f4e3b67

Rene Krenn

2537819f0d

MT#12643 billing networks and multi bill prof WIP

-properly validate billing mapping intervals
-api/contracts and api/customers complete
 +the problem with updating the "prepaid" preference remains at the moment
 +billing_mappings field contains future (editable) mappings only, the full schedule is given in a separate field
 +hal-links to all occurring billing profiles and networks
-extended tests: api-customer.t and api-contract.t
-api-billingnetworks.t test
-billing networks panel controller
 +search by enclosed IP address
-panel UIs for billing networks, customers, contracts
 +past billing mapping intervals that cannot be edited are displayed by a seperate hfh "block" part of the billing_profiles repeatable
-profile packages api, UI
 +terminating billing profiles (MT#8645) will be broken
  +fixed now: profile cannot be terminated unless there are:
   -zero non-terminated customers, whose mappings contain the profile with future or open end
   -zero profile packages, that link to the profile in either one of their initial-, underrun- or topup profile sets
 +panel edit should work, termination wip
 +topup_profiles w/o amounts
+contracts/customers API profile_package_id field:
 +apply the package's initial profiles
 +api/customer and api/contract profile definition modes (id/profiles/package)
 +api OK, api-customer.t tests
 +customer and contract panel UI with selector to specify actual billing mapping, schedule or profile package (same as api)
+terminate logic harmonized: profiles, networks, packages
+api tests updated
+prepare for merging: cleanup, enable tests

Change-Id: I6c0dec72f490b5731fc673cd393d6aeb08dd8143

3 Commits (ba2894de4827024185975d6a712ca8017e52b00b)