Update ALBResult in aws-lambda

[donaldpipowitch]

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

Select one of these and delete the others:

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: <>
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
• Include tests for your changes
• If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.

---

As far as I can tell statusDescription and isBase64Encoded are optional. E.g. statusDescription is also not a part of this official example: https://github.com/aws/elastic-load-balancing-tools/blob/master/application-load-balancer-serverless-app/whatismyip/whatismyip.py#L14

But I'm not super familiar with the API. There are several old blog post which says that those fields are required, but my tests can't verify this. Same results for me if I drop those fields? Maybe ALB changed it's behavior?

[typescript-bot]

@donaldpipowitch Thank you for submitting this PR!

This is a live comment which I will keep updated.

This PR doesn't modify any tests, so it's hard to know what's being fixed, and your changes might regress in the future. Have you considered adding tests to cover the change you're making? Including tests allows this PR to be merged by yourself and the owners of this module. This can potentially save days of time for you.

Code Reviews

This PR can be merged once it's reviewed by a DT maintainer.

Status

• ✅ No merge conflicts
• ✅ Continuous integration tests have passed
• ❌ Only a DT maintainer can merge changes without tests

Once every item on this list is checked, I'll ask you for permission to merge and publish the changes.

---

Diagnostic Information: What the bot saw about this PR

{
  "type": "info",
  "now": "-",
  "pr_number": 45936,
  "author": "donaldpipowitch",
  "owners": [
    "darbio",
    "skarum",
    "StefH",
    "tobyhede",
    "buggy",
    "y13i",
    "wwwy3y3",
    "OrthoDex",
    "MichaelMarner",
    "daniel-cottone",
    "kostya-misura",
    "coderbyheart",
    "palmithor",
    "daniloraisi",
    "simonbuchan",
    "Haydabase",
    "repl-chris",
    "aneilbaboo",
    "jeznag",
    "louislarry",
    "dpapukchiev",
    "ohookins",
    "trevor-leach",
    "jagregory",
    "dalen",
    "loikg",
    "skyzenr",
    "redlickigrzegorz",
    "juancarbonel",
    "pwmcintyre",
    "alex-bolenok-centralreach",
    "marianzange",
    "apepper",
    "apalumbo",
    "SachinShekhar",
    "ivanmartos",
    "zach-anthony"
  ],
  "dangerLevel": "ScopedAndUntested",
  "headCommitAbbrOid": "96d0a76",
  "headCommitOid": "96d0a76490511813bda14fdb0d241b93647dfb46",
  "mergeIsRequested": false,
  "stalenessInDays": 2,
  "lastPushDate": "2020-07-07T19:17:19.000Z",
  "lastCommentDate": "2020-07-07T19:17:19.000Z",
  "maintainerBlessed": false,
  "reviewLink": "https://github.com/DefinitelyTyped/DefinitelyTyped/pull/45936/files",
  "hasMergeConflict": false,
  "authorIsOwner": false,
  "isFirstContribution": false,
  "popularityLevel": "Popular",
  "anyPackageIsNew": false,
  "packages": [
    "aws-lambda"
  ],
  "files": [
    {
      "path": "types/aws-lambda/trigger/alb.d.ts",
      "kind": "definition",
      "package": "aws-lambda"
    }
  ],
  "hasDismissedReview": false,
  "ciResult": "pass",
  "lastReviewDate": "2020-07-07T23:49:54.000Z",
  "reviewersWithStaleReviews": [],
  "approvalFlags": 2,
  "isChangesRequested": false
}

[typescript-bot]

🔔 @darbio @skarum @StefH @tobyhede @buggy @y13i @wwwy3y3 @OrthoDex @MichaelMarner @daniel-cottone @kostya-misura @coderbyheart @palmithor @daniloraisi @simonbuchan @Haydabase @repl-chris @aneilbaboo @jeznag @louislarry @dpapukchiev @ohookins @trevor-leach @jagregory @dalen @loikg @skyzenr @redlickigrzegorz @juancarbonel @pwmcintyre @alex-bolenok-centralreach @marianzange @apepper @apalumbo @SachinShekhar @ivanmartos @zach-anthony - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

[typescript-bot]

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊

	master	#45936	diff
Batch compilation
Memory usage (MiB)	74.8	74.8	+0.1%
Type count	10976	10976	0%
Assignability cache size	2327	2327	0%
Language service
Samples taken	2026	2066	+2%
Identifiers in tests	3188	3188	0%
getCompletionsAtPosition
Mean duration (ms)	355.9	354.7	-0.3%
Mean CV	7.9%	7.7%
Worst duration (ms)	475.4	468.6	-1.4%
Worst identifier	CodeBuildCloudWatchStateEvent	logs
getQuickInfoAtPosition
Mean duration (ms)	358.1	356.7	-0.4%
Mean CV	8.2%	8.1%	-1.5%
Worst duration (ms)	459.2	496.5	+8.1%
Worst identifier	snsEventCodeBuildStateHandler	codeBuildStateEventDetail

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

[simonbuchan]

The documentation is pretty poor in general about lambda triggers. This seems fine to me since you've tested it working without them!

[typescript-bot]

I just published @types/aws-lambda@8.10.59 to npm.