Adding additional metadata to the response of a POST /hashes

[michael-iglesias]

Ability to specify a CHAINPOINT_NODE_PRIVATE_URI env var that is to be used in conjunction with the additional metadata included in the response body of any call to POST /hashes when a corresponding CHAINPOINT_NODE_REFLECTED_URI env variable is also set.

Code Changes

• Introduced CHAINPOINT_NODE_PRIVATE_URI env var
• Added a validation function to validate CHAINPOINT_NODE_PRIVATE_URI if a value is provided
• Introduced CHAINPOINT_NODE_REFLECTED_URI env var
• Added a validation function to validate CHAINPOINT_NODE_REFLECTED_URI if a value is provided
• Edited POST /hashes metaDataObject to include a 'uri' property when the conditions of including said value are met

Test Cases

• CHAINPOINT_NODE_PRIVATE_URI=http://10.0.0.1 & CHAINPOINT_NODE_REFLECTED_URI=private ----> PASSES
• Omit CHAINPOINT_NODE_PRIVATE_URI & CHAINPOINT_NODE_REFLECTED_URI ----> PASSES
• CHAINPOINT_NODE_PRIVATE_URI=http://google.com & CHAINPOINT_NODE_REFLECTED_URI=private ----> throws error
• CHAINPOINT_NODE_PRIVATE_URI=http://10.0.0.1 & CHAINPOINT_NODE_REFLECTED_URI=foobar ----> throws error
• CHAINPOINT_NODE_PRIVATE_URI= & CHAINPOINT_NODE_REFLECTED_URI=private ----> throws error

Steps to Test

1. Add an env variable "CHAINPOINT_NODE_PRIVATE_URI" with a valid RFC1918 IP Address
2. Add an env variable "CHAINPOINT_NODE_REFLECTED_URI" with a value of "public" or "private"
3. Make a CURL request to POST /hashes and assert that a new property labeled "uri" has been included in the "meta" nested object of the response body

[grempe]

Merged. Thanks @michael-iglesias