Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-21545

Change validation behaviour of redundant fields for various API objects

XMLWordPrintable

    • Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Sprint 106 (Nov 2023), Sprint 107 (Dec 2023), S2401, S24-W12/13, S24-W18/19
    • 3

      The introduction of more strict API validation of fields passed as input (for mostly create/update methods) interferes with template import and adds additional requirements to frontend to leave out fields not applicable to specific entities according to their type, whether they stem from a template, are inherited or discovered, etc.

      Conditions of API_UNEXPECTED should be reworked to accept database record defaults - for import.

      Frontend should be reworked with additional conditions to collect only those fields that are applicable to the current entity type and state,, prohibiting passing of additional fields (e.g. ones marked disabled/hidden, but currently can still be fed in for updates where not appropriate).

            vmaksimovs Vladimirs Maksimovs
            vmaksimovs Vladimirs Maksimovs
            Team C
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: