Why will & and # be eliminated in 2.3 / 2.4? Is there a tool to convert all of our existing triggers that contain those booleans.......?

XMLWordPrintable

    • Type: Incident report
    • Resolution: Won't fix
    • Priority: Major
    • None
    • Affects Version/s: 2.3.1
    • Component/s: Installation (I)
    • Environment:
      Linux servers, 8 proxies, currently on 2.2.2, 67,000 triggers.

      Since this change will make a great number of our triggers invalid, will there be an easy upgrade path to convert them to the new syntax? If not, this will cause a major disruption in our monitoring.

      I put this in the Bug category because it will break monitoring when it happens.

            Assignee:
            Unassigned
            Reporter:
            Bill Kowalewski-Barrera
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: