Jeff

Streamline the Development Environment Setup.

3

I wanted to take a step forward in the "get a dev started quickly" direction. This PR includes several Makefile targets, as well as a few install scripts to quickly...

There is a lot of re-used code in the split-up AWS Targets. We should move this code to a shared `common` folder.

``` - name: controller terminationMessagePolicy: FallbackToLogsOnError image: ko://github.com/triggermesh/triggermesh/cmd/triggermesh-controller resources: ``` Introduced through: [DocId: 0] › spec › template › spec › containers[controller] › livenessProbe This issue is... Liveness probe is...

Try it out: On github: * Select `Code` in the top right of the repository * Select `Codespaces` * Select `Create Codespace` Via vscode and Docker: * Checkout the repo...

:S3 Target: Removes the Event Source From the File/Naming Structure

3

Previously we included the event source as part of the path that we place the file. We could spend some time figuring out a fun way to sanitize special characters...

AWS S3 Target Does Not Properly Sanitize Blob Name

1

This line should be checked for bad returns. Including un-escaped characters. https://github.com/triggermesh/triggermesh/blob/5da18fa55b7f8c85555907774697a46b47075897/pkg/targets/adapter/awss3target/adapter.go#L115

Currently, the naming of the spec parameters for the credentials do not match with our AWS Source and Targets. see: * https://github.com/triggermesh/triggermesh/blob/main/config/samples/targets/aws/200-aws-sqs-target.yaml * https://github.com/triggermesh/triggermesh/blob/main/config/samples/sources/awssqssource.yaml

Adds in some notes on events in the dev docs, as well as the expected schema in the `schemas` directory. It also includes a sample configuration/deployment file.

KafkaTarget Should Implement the TM Replier Package

2

The Kafka Target adapter should be updated to use the common 'replier' package.