Changeset 915 for trunk/cgi-bin/IPDB.pm

Timestamp:

04/27/18 15:28:45 (6 years ago)

Author:

Kris Deugau

Message:

/trunk

Start adding a generalized in-your-face infonotice space to attach warnings
to a netblock. See #17 and #23, sort of.

• table to hold the notices, since they're likely to be far fewer than the overall allocation count
• show any notices for the parent chain for new allocations in the admin tools

File:

• trunk/cgi-bin/IPDB.pm (modified) (3 diffs)

trunk/cgi-bin/IPDB.pm

@@ -35 +35 @@
         &getBlockRDNS &getRDNSbyIP &getRevID
         &getNodeList &getNodeName &getNodeInfo
+        &getBlockNotices
         &mailNotify
         );
@@ -51 +52 @@
                 &getBlockRDNS &getRDNSbyIP &getRevID
                 &getNodeList &getNodeName &getNodeInfo
+                &getBlockNotices
                 &mailNotify
                 )]
@@ -3553 +3555 @@
 
 
+## IPDB::getBlockNotices()
+# Retrieve any infonotes for a block and all of its parents
+# Takes the block ID to trace down the stack
+# Returns an arrayref to the block and all of its parents, containing the CIDR,
+# description, and notice (if any) associated to each block.
+sub getBlockNotices {
+  my $dbh = shift;
+  my $bid = shift;
+  my $nlist = $dbh->selectall_arrayref(q(
+        WITH RECURSIVE blockparents (id, cidr, description, parent_id, notice, depth) AS (
+                SELECT a.id, a.cidr, a.description, a.parent_id, bn.notice, 1 AS depth FROM allocations a
+                LEFT JOIN blocknotices bn ON a.id = bn.alloc_id
+                WHERE a.id = ?
+                UNION
+                SELECT b.id, b.cidr, b.description, b.parent_id, bn2.notice, t.depth AS depth FROM allocations b
+                JOIN blockparents t ON t.parent_id = b.id
+                LEFT JOIN blocknotices bn2 ON b.id = bn2.alloc_id
+        ) SELECT id, cidr, description, parent_id, notice FROM blockparents ORDER BY depth DESC;
+), {Slice=>{}}, $bid);
+
+  return $nlist;
+} # end getBlockNotices()
+
+
 ## IPDB::mailNotify()
 # Sends notification mail to recipients regarding an IPDB operation