[Fix] Moved AWS loading till after config is resolved

AWS::CodeDeployCommand requires that runtime configurations be resolved before it is able to accurately load up its API definition. This update allows the Windows version of the Agent to provide AWS::CodeDeployCommand the opportunity to resolve those config settings with minimal impact to the wider codebase.

Author: dljvette

lib/winagent.rb

@@ -10,7 +10,6 @@
 require 'instance_agent/log'
 require 'instance_agent/platform'
 require 'instance_agent/platform/windows_util'
-require 'instance_agent/plugins/codedeploy/register_plugin'
 require 'pathname'
 
 include Win32
@@ -102,4 +101,11 @@ def with_error_handling
   end  
 end
 
+# InstanceAgentService loads in a set of configurations that are assumed by the CodeDeploy plugin registery to be in place when the
+# the classes are loaded. This happens to be true for the Linux agent as `GLI::App.pre` loads up the config before resolving additional
+# gem dependencies. However, Aws.add_service requires that the service be defined when the gem is loaded so there is not an efficient way
+# to resolve this at runtime; thus, the config must be resolved before the CodeDeployCommand class is loaded.
+InstanceAgentService.new.read_config unless defined?(Ocra)
+require 'instance_agent/plugins/codedeploy/register_plugin'
+
 InstanceAgentService.mainloop unless defined?(Ocra)

vendor/gems/codedeploy-commands-1.0.0/lib/aws/add_service_wrapper.rb

@@ -43,7 +43,6 @@ def self.add_service(name, options = {})
             module_name: module_name,
             api: api_hash,
             paginators: options[:paginators],
-            paginators: options[:paginators],
             waiters: options[:waiters],
             resources: options[:resources],
             gem_dependencies: { 'aws-sdk-core' => '3' },