Add IoTCoreMQTTMessage to aws/aws-lambda-go/events

Open
#542 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cloud

Research direction

Start in /aws/aws-lambda-go/events and review the existing event types before assessing IoTCoreMQTTMessage and IoTCoreMQTTState. Confirm the complete IoTCore-forwarded MQTT payload schema, including the fields represented by the ellipses and the clientd tag, then define what a complete event type should cover.

Written by the indexing model from the issue text.

Description

enhancement type/events

Is your feature request related to a problem? Please describe.
Missing type to handle MQTT messages forwarded by IoTCore

Describe the solution you'd like
Add a new type to /aws/aws-lambda-go/events, for example:

type IoTCoreMQTTMessage struct {
	State    IoTCoreMQTTState `json:"state"`
	Topic    string           `json:"topic"`
	ClientId string           `json:"clientd"`
	// ...
}
type IoTCoreMQTTState struct {
	Reported  map[string]interface{} `json:"reported"`
	// ...
}

Describe alternatives you've considered
The user defines the type by himself

Dominant language
Go
Stars
3.8k
Forks
578
Avg merge
16h 56m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-go

All issues in aws/aws-lambda-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.