schisamo
Repos
88
Followers
108
Following
31

Events

opened issue
Link targets incorrect on "Install the Datadog Agent on Kubernetes" page

Documentation Page

The main Install the Datadog Agent on Kubernetes page.

I've seen the issue on the latest version of Safari and Firefox on my MBP.

Issue Description

The links on the second two tabs (Helm, DaemonSet) are completely wrong. For example:

  • Install Helm goes to https://github.com/DataDog/datadog-operator but should be going to https://v3.helm.sh/docs/intro/install/
  • Datadog Helm repository README goes to https://docs.datadoghq.com/agent/guide/operator-advanced but should be going to https://github.com/DataDog/helm-charts/blob/master/charts/datadog

Looking over the source code for the file it appears the nesting of the reference-style links isn't working as expected.

Created at 1 week ago
Created at 2 weeks ago
Created at 3 weeks ago
Created at 3 weeks ago
opened issue
[FEATURE] send_message_public_channel metadata event payload should accept either a string or JSON object

Is your feature request related to a problem? Please describe. Full details on #4145

Describe the solution you'd like The Metadata Event Payload input property on the send_message_public_channel step accepts both a string or JSON object.

Do you have a workaround? Yes. JSON.stringify can be used to convert the JSON object to a string.

Created at 1 month ago
issue comment
[BUG] Can't pass valid JSON to send_message_public_channel metadata event payload

@ctrlaltdylan That worked! Sorry for the noise.

Created at 1 month ago
opened issue
[BUG] Can't pass valid JSON to send_message_public_channel metadata event payload

Describe the bug The send_message_public_channel Workflow step will not accept dynamic valid JSON objects in the Metadata Event Payload config input. This config is expected valid JSON. From the error being returned it appears Pipedream is attempting to parse the valid JSON an additional time.

To Reproduce Steps to reproduce the behavior:

  1. Create a workflow.
  2. Add a send_message_public_channel step
  3. Configure the Metadata Event Payload value using valid dynamic JSON data from a previous step.
  4. See the following error when the workflow executes:
Invalid JSON in metadata_event_payload: Unexpected token o in JSON at position 1

Expected behavior I would expect the valid dynamic JSON payload to be properly parsed and passed along as the Metadata Event Payload input.

Screenshots pipedream_error

Created at 1 month ago
Created at 1 month ago
Created at 1 month ago
Created at 1 month ago
Created at 1 month ago
Created at 1 month ago
started
Created at 1 month ago
Created at 1 month ago
Created at 2 months ago
started
Created at 2 months ago
started
Created at 2 months ago
started
Created at 2 months ago
Created at 2 months ago
Created at 2 months ago
Created at 2 months ago
started
Created at 2 months ago