# Copyright (c) 2021 Contrast Security, Inc. See https://www.contrastsecurity.com/enduser-terms-0317a for more details.
# frozen_string_literal: true

require 'contrast/agent/reaction_processor'

module Contrast
  module Api
    module Communication
      # Handles processing deferred messages
      class ResponseProcessor
        include Contrast::Components::Interface
        access_component :agent, :analysis, :logging, :settings

        # @param response [Contrast::Api::Settings::AgentSettings]
        def process response
          logger.debug('Received a response', sent_ms: response&.sent_ms)

          server_features = process_server_response(response)
          app_settings = process_application_response(response)

          # ReactionProcessor is a design pattern from TeamServer.
          # Right now, there's one potential reaction, which is disabling the agent
          Contrast::Agent::ReactionProcessor.process(response&.application_settings)

          Contrast::Logger::Log.instance.update(server_features&.log_file, server_features&.log_level)
          update_features(server_features, app_settings)
          logger.trace(
              'Agent settings updated in response to Service',
              protect_on: PROTECT.enabled?,
              assess_on: ASSESS.enabled?)
        end

        private

        # Given some protobuf messages, update server features.
        # This is the bridge between Contrast Service <-> Settings.
        #
        # @param response [Contrast::Api::Settings::AgentSettings]
        def process_server_response response
          server_features = response&.server_features
          return unless server_features

          logger.trace('Agent: Received updated server features')

          SETTINGS.update_from_server_features(server_features)

          server_features
        end

        # Given some protobuf messages, update application settings.
        # This is the bridge between Contrast Service <-> Settings.
        #
        # @param response [Contrast::Api::Settings::AgentSettings]
        def process_application_response response
          app_settings = response&.application_settings
          return unless app_settings

          logger.debug('Agent: Received updated application settings')

          SETTINGS.update_from_application_settings(app_settings)

          app_settings
        end

        # This can't go in the Settings component because protect and assess depend on settings
        # I don't think it should go into contrast_service because that only handles connection specific data
        def update_features server_features, app_settings
          return unless !!(server_features || app_settings)
          return unless AGENT.enabled?

          logger.trace_with_time('Rebuilding rule modes') do
            SETTINGS.build_protect_rules if PROTECT.enabled?
            AGENT.reset_ruleset

            logger.info('Current rule settings:')

            PROTECT.rules.each { |k, v| logger.info('Protect Rule mode set', rule: k, mode: v.mode) }
            logger.info('Disabled Assess Rules', rules: ASSESS.disabled_rules)
          end
        end
      end
    end
  end
end