[GitHub] [netbeans] peedeeboy opened a new pull request #1312: [NETBEANS-2400] Fix for AWS Cloud missing Regions

[GitBox <gi...@apache.org>]

peedeeboy opened a new pull request #1312: [NETBEANS-2400] Fix for AWS Cloud missing Regions
URL: https://github.com/apache/netbeans/pull/1312
 
 
   
   What this PR does
   =================
   * Updates AWS regions in NB to include all current AWS regions
   * Updates AWS Java SDK to 1.11.569 - needed as newer regions use v4 signing protocol
   * Enables creation of JavaEE 7 applications when AWS container is running Tomcat 8.x
   * Filters available AWS Containers to only those running Tomcat
   
   Controversies!
   ============
   * AWS Java SDK 1.11.569 moves/removeds some classes/methods.  This causes the NB sigtest to abort the build.  I don't think the AWS SDK will ever be really stable in the way NB's internal APIs usually are (especially when we jump to AWS SDK v2), so I have added the sigtest.gen.fail.on.error=false project property to ignore the sigtest errors...
   * I have not updated the org.apache.commons.codec and org.apache.commons.logging modules with new .jar files.  From my testing, the AWS SDK worked fine with the current libraries.  If the AWS modules are expanded, these may need to be updated if any new methods/classes are consumed..
   
   Files Changed
   =============
   Amazon Elastic Beanstalk Module
   -------------------------------
   * AmazonDeploymentFactory.java - Passes regionCode into new AmazonDeploymentManager instances
   * AmazonInstance.java - Uses the new Client Builder classes (which require the Region Code, rather than Endpoint) rather than the now deprecated constructors.  Creates a default instance profile with sensible (?) values, as the Java SDK doesn't create one by default!
   * AmazonInstanceTest.java - Now uses system temp directory rather than hardcoded path and is altered for modified AmazonInstance constructor
   * AmazonJ2EEServerInstanceProvider.java - Now also stores Region Code in properties
   * AmazonWizardComponent.java - Contains full list of current AWS instances and also includes their Region Code
   * AmazonDeploymentManager.java - Passes in Region Code to AmazonInstance when deploying an application
   * AmazonJ2eePlatformImpl2.java - Now checks if Container is running Tomcat 8.x and if so allows creation of Java EE 7 application
   * Project.xml - Module now depends on Amazon SDK module 1.16
   * AmazonInstanceManager.java - Now stores Region Code in instance properties
   * AmazonWizardPanel.java - Now stores Region Code in properties
   * AmazonWizardIterator.java - Passes Region Code into AmazonInstanceManager 
   * ViewAdminConsoleAction.java - Uses Region Code to generate URL, rather than parsing Endpoint
   * AmazonJ2EEServerWizardComponent - Filters AWS Containers to only those running Tomcat
   
   Amazon SDK Module
   -----------------
   * binaries-list - Removed references to old dependencies, and added Maven central references for new dependecies
   * project.xml - Dependencies updated
   * manifest.mf - API version updated to 1.16
   * project.properties - Added sigtest.gen.fail.on.error=false to prevent sigtest stopping the build due to deprecated/removed methods in the SDK.  Updated dependency locations
   * Several license files removed & added
   
   
   Testing
   =======
   * If running from NB, build Amazon SDK module, then Amazon Elastic Beanstalk module.  Otherwise, build NB.
   * In NB, Services tab -> Cloud -> Right-click -> Add Cloud...
   * Cloud: Amazon Beastalk -> Next -> Pick a region (check all AWS regions now in dropdown) -> Enter Key ID and Secret Access Key -> Next -> Finish
   * File menu -> New Project -> Java with Maven -> Web Application -> Next >
   * Complete Name & Location Details -> Next >
   * Click Add next to Server
   * Choose Server = Amazon Beanstalk -> Next >
   * Complete Application Name, Environment Name & Environment URL fields
   * Pick the Container running Amazon Linux 3.1.6 & Tomcat 8.5
   * Click Finish
   * Make sure new Server is selected in dropdown and Java EE version = Java EE 7 Web -> Finish
   
   * Services tab -> AWS Beanstalk node -> Right-click -> Open AWS Console
   * Log in to AWS.  Go and make a cup of tea whilst you wait for the new Environment to start (status = Green), takes ~ 5 minutes
   * AWS Beanstalk node -> Right-click -> Refresh.  Under the Servers node, the AWS Tomcat node show now show running icon
   
   * Projects -> Right-click on project -> Run
   * Go and make another cup of tea whilst AWS reconfigures (~ 3 minutes)
   * Check output and make sure deployment successful.  
   * Browser will open.  Most likely a blank page.  Refresh and application should be displayed...
   
   Don't forget to Terminate the environment and delete the application in AWS control panel!!
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists