Skip to content
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.

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

HTTP Keyword - dynamic value in XML/JSON request body #3986

Closed
2 tasks done
marcolonghitano opened this issue Nov 6, 2023 · 4 comments
Closed
2 tasks done

HTTP Keyword - dynamic value in XML/JSON request body #3986

marcolonghitano opened this issue Nov 6, 2023 · 4 comments
Labels
area:monitor Everything related to monitors feature-request Request for new features to be added type:enhance-existing feature wants to enhance existing monitor

Comments

@marcolonghitano
Copy link

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I would like to add a dynamic value in the body request.
I know it's possible to check the response with JSONata, I need something similar to create a dynamic JSON/XML body with the current timestamp. For instance:

{
  "parameter": $now()
}

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.3

💻 Operating System and Arch

Ubuntu 18.04.1

🌐 Browser

Chrome

🐋 Docker Version

No response

🟩 NodeJS Version

No response

Copy link

github-actions bot commented Feb 4, 2024

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions github-actions bot added the Stale label Feb 4, 2024
@CommanderStorm CommanderStorm added feature-request Request for new features to be added area:monitor Everything related to monitors type:enhance-existing feature wants to enhance existing monitor and removed help Stale labels Feb 4, 2024
@CommanderStorm
Copy link
Collaborator

Reassigned as feature-request instead of a help issue.

Unsure how to implement this

  • without being too bad for maintenance
  • without being backwards-breaking

@chakflying
Copy link
Collaborator

We can basically group this together with #4383 by providing a template language (liquid.js) for the request body input.

@CommanderStorm
Copy link
Collaborator

Agree, merging into #4383 and making said issue a bit more generic.
=> closing as a "duplicate"

@CommanderStorm CommanderStorm closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:monitor Everything related to monitors feature-request Request for new features to be added type:enhance-existing feature wants to enhance existing monitor
Projects
None yet
Development

No branches or pull requests

3 participants