matt beary

This is still needed

for some clarification - codepipeline artifacts lose their access timestamps, which stops `dotnet package`'s normal re-packaging detection/prevention from working

The ability to re-use the same artifact across dev and prod environments, rather than having to rebuild them, is still needed

This can be worked around by using `aws cloudformation package` instead of `dotnet lambda package-ci`: 1. build your template using `AWS::Serverless::Function` objects either using `CodeUri` directly or via the `Globals`....

Hello, It's been over a year since I've really looked at this repository, and I'm not currently doing any work with lambdas, so it's unlikely that I'll be able to...

@samkeeleyong AFAICT they haven't done the legal legwork to accept contributions (e.g. relicensing agreement), so they need to either do that or rewrite similar changes themselves: `Ping Identity does not...

to clarify a bit, while section 2.4 recommends "service providers SHOULD canonicalize the value returned", they are not required to do so. I have raised [an issue with wso2](https://github.com/wso2/product-is/issues/3426) to...

This is sorta related to #81

I'm not certain there's value in any of the upstream tags, honestly. Having tags that align with Framework's releases are the ones that matter, so we can try use a...

Exposing it via `/sys/class/leds` could also be nice (because we could set up keybinds), but the possibility of that is deeper than my firmware knowledge goes.