nathan-d / emea-build-hackday Goto Github PK

We should drop in a nice FAWS or Rackspace favicon as a web apps asset.

Our form fields don't perform any validation. We should add in the following:

• Field content type validation
• Handle account validation and checks in the backend
  • Perform notification actions where a submission was against an invalid account, etc.

The application should support the scoring functionality currently available in the excel document.

Requirements

• Support scoring system as found in the Excel document
• Display the selected services and processed score prior to submission
• Use colour coding (Green, Amber, Red) for service groups

We should investigate if its possible to create new JIRA cards on the successful submission of a Simple Build.

To ensure this drops into the Simple Builds JIRA swimlane the card will need the respective label added.

Our application's submission functionality is currently just a stub. This functionality needs to be added.

We should add a lambda function to process the form data, removing unnecessary fields, and submitting it to DynamoDB.

Now we've got the project working and build via the console, lets make it work with Cloudformation. This will allow the project to be reused as a demo and for other initiatives.

The review pane is pretty basic. We need to hide sections that don't have any selected services.

As suggested by @Fresno16 - we should pull the services score and associated data from the database on form load. We can do this by exposing this data via an API endpoint.

Note that the form should be able to handle latency gracefully and the inability to access the endpoint by notifying the user.

The python lambda function created during the hackday needs some refactoring to make it a little more defensive in its queue processing and include proper error handling.

LucidChart's graphs API will allow us to see what products are being used in each infrasturcture design.

https://www.lucidchart.com/pages/api_graph

Worth looking into at some point.

We should support Racker authentication via RSA tokens.

Field to be added for AWS Spend to this page only spends < $4k can proceed.

Looks like the spend field is reusing a field rather than having it own.

See issue #23 for data structure change issue. We'll need to traverse another level down to find the selected key value.

The progress bar only exists in the context of the customer form at this point. If this is intended for use in application it should be present in the parent form with progress tied to form component rather than in the form component itself.

As a team create a architectural document to work from.

To remove the need for the SA/SE emailing the build team we should look to add support for the uploading of HLP documents via the form.

HLP documents should be uploaded to a private S3 bucket and a reference added to the DynamoDB row.

On successful processing of a Simple Builds message we should perform the following notification actions:

1. Send an email to the build team and the submitting SA stating the build has been successfully submitted and should be reviewed by a build engineer.
2. Notify the submitting SA where the submissions failed validation checks as per issue #18 (If we implement this feature).
3. Send a Slack message to the FAWS Build Team channel.

Selecting a product results in a pretty catastrophic styling break.