Standalone Ripple FIM Services

[shawncrawley]

This PR implements the following standalone Ripple FIM services:

• ana_inundation_extent_rasfim_noaa
• mrf_nbm_5day_max_inundation_extent_rasfim_noaa
• rfc_based_5day_max_inundation_extent_rasfim_noaa

This introduces the following new AWS Resources:

• hv-vpp-*-viz-ripple-fim-processing lambda function
• hv-vpp-*-viz-ripple-fim-data-prep lambda function
• hv-vpp-*-ripple-fim-processing step function

This modifies the hv-vpp-*-viz-pipeline step function by now referencing the hv-vpp-*-ripple-fim-processing step function within the fim processing section. There's a new data path that will execute this step function if $.fim_config.fim_type contains "ripple".

[shawncrawley]

@LorneLeonard-NOAA I made some tweaks to Core\LAMBDA\viz_functions\ripple_fim_processing\deploy\code\lambda_function.py based on comments/feedback by Nick and Ryan. Namely, I turned the various debugging/tracking variables into environment variables that are not actually set via terraform, but are accessed via code with defaults that yield appropriate behavior in ti, uat, and prod. These environment variables can be added manually to your own version of the Lambda.

View the names and expected values/defaults of these environment variables in the code here:

hydrovis/Core/LAMBDA/viz_functions/ripple_fim_processing/deploy/code/lambda_function.py

Lines 31 to 35 in e9e1036

	ENV_UPLOAD_TRACKING = os.getenv('UPLOAD_TRACKING', 'false').lower() == "true"
	ENV_CONSOLE_DEBUGGING = os.getenv('CONSOLE_DEBUGGING', 'false').lower() == "true"
	ENV_CONSOLE_DEBUGGING_FOR_EVERY_TIF = os.getenv('CONSOLE_DEBUGGING_FOR_EVERY_TIF', 'false').lower() == "true"
	ENV_DB_TRACKING_SCHEMA = os.getenv("DB_TRACKING_SCHEMA", "dev")
	ENV_DB_TRACKING_TABLE_NAME = os.getenv("DB_TRACKING_TABLE_NAME", "ripple_model_tracker")