-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
* Feat/lambda with basic defaults (#7474) * plugins/aws: Non-functional format changes to aws * plguins/aws: reformat oss perroute to accept additional parameters and add new settings option for driving this behavior * plugins/aws: Testing showing that there is an issue with implementation * plugins/aws: Testing without blowing away the entire destinations * plugins/aws: Route level destination spec settings can be inherited from upstream spec * plugins/aws: Codegen getters * plugins/aws: Add comment * plugins/aws: Null checks on destinations * plugins/aws: Cleaner comments * plugins/aws: Update naming and better descriptions * aws: Update naming and comments per review * aws: Update naming and comments per review * changelog: update Co-authored-by: soloio-bulldozer[bot] <48420018+soloio-bulldozer[bot]@users.noreply.github.com> * codegen * update change type to NON_USER_FACING since patch bump * empty commit * expand m1 setup support - remove race image setup for m1 * Expose fallbackToFirstFunction helm (#7575) * expose fallbackToFirstFunction helm * add changelog * update changelog + add aws fallback tests * codegen * empty commit * update changelog * update changelog Co-authored-by: soloio-bulldozer[bot] <48420018+soloio-bulldozer[bot]@users.noreply.github.com> * delete changelog * Adding changelog file to new location * Deleting changelog file from old location * Fix destinationOverrides not being applied to empty aws destination (#7583) * fix issue with overrides not being applies to unset destinationSpec * add changelog * remove unecessary dest.DestinationType * add tests + move 'no spec' tests to own context * empty commit * aws: Update plugin comments for the new fallback behaviors * aws: Update naming of plugin variables, make a new possible err set if somehow an upstream erroneously had aws set * fix comment nits + return * review fix Co-authored-by: nfuden <[email protected]> Co-authored-by: soloio-bulldozer[bot] <48420018+soloio-bulldozer[bot]@users.noreply.github.com> Co-authored-by: Nathan Fudenberg <[email protected]> Co-authored-by: soloio-bulldozer[bot] <48420018+soloio-bulldozer[bot]@users.noreply.github.com> Co-authored-by: changelog-bot <changelog-bot>
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
changelog: | ||
- type: NON_USER_FACING | ||
description: > | ||
Add option that allows usage of lambda upstreams without specifying a function. | ||
Affects custom extensions of the lambda extension built in go that use gloo as a library. | ||
This is purely a work around for current Gloo Portal behavior and likely should not be opted into otherwise. | ||
issueLink: https://github.com/solo-io/solo-projects/issues/4274 | ||
resolvesIssue: false | ||
- type: NON_USER_FACING | ||
description: Aws lambda set upstream level defaults to override route destinations. | ||
issueLink: https://github.com/solo-io/solo-projects/issues/4274 | ||
resolvesIssue: false |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.