Skip to content

fix(flows): support parameter keys with dashes #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
reubenmiller merged 1 commit into from
Mar 3, 2026
Merged

fix(flows): support parameter keys with dashes #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/parameter_update.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ case "$COMMAND" in
exit 1
fi

PARAMETER_PAYLOAD=$(echo "$MESSAGE" | jq ".operation.${TYPE}")
PARAMETER_PAYLOAD=$(echo "$MESSAGE" | jq ".operation.\"${TYPE}\"")

echo :::begin-tedge:::
printf '{"type":"%s","parameters":%s}\n' "$TYPE" "$PARAMETER_PAYLOAD"
Expand Down
11 changes: 7 additions & 4 deletions src/plugins/flow_params
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,14 @@ update_parameters() {

# convert json to key/value and write it to the params.toml file
echo "Writing to the flows params.toml file. path=$FLOW_DIR/params.toml" >&2
echo "$MESSAGE" | jq -r 'to_entries|map("\(.key) = \(.value|tojson)")|.[]' | sudo tedge-write "$FLOW_DIR/params.toml"
CONTENTS=$(echo "$MESSAGE" | jq -r 'to_entries|map("\(.key) = \(.value|tojson)")|.[]')
if [ -n "$CONTENTS" ] && [ "$CONTENTS" != "null" ]; then
echo "$MESSAGE" | jq -r 'to_entries|map("\(.key) = \(.value|tojson)")|.[]' | sudo tedge-write "$FLOW_DIR/params.toml"

# Note: manually update the digital twin property though normally this is done by the Device Parameter microservice
# as sending the 408 message is actually harder than just updating the digital twin value
tedge mqtt pub -r "te/device/main///twin/$MESSAGE_TYPE" "${MESSAGE}"
# Note: manually update the digital twin property though normally this is done by the Device Parameter microservice
# as sending the 408 message is actually harder than just updating the digital twin value
tedge mqtt pub -r "te/device/main///twin/$MESSAGE_TYPE" "${MESSAGE}"
fi
}

get() {
Expand Down
Loading