Add a member to a Telegraf config in Influxdata Influx OSS

What this operation does

Add a member to a Telegraf config

• POSTChanges data · Telegrafs/telegrafs/{telegrafID}/members

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Influxdata Influx OSS operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Influxdata Influx OSS operations

• Create a new taskPOST · changes data
• Create a userPOST · changes data
• Add new checkPOST · changes data
• Create a new stackPOST · changes data
• Manually start a task run, overriding the current schedulePOST · changes data
• Add a label to a taskPOST · changes data
• Add an owner to a taskPOST · changes data
• Add a notification rulePOST · changes data

All 197 Influxdata Influx OSS operations

Questions

Can HumDay add a member to a telegraf config in Influxdata Influx OSS?

Yes. This operation is published in Influxdata Influx OSS's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Influxdata Influx OSS data?

Yes — this is a POST operation, so it changes something in Influxdata Influx OSS. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Influxdata Influx OSS account.

Where this came from

Read from a published API description for Influxdata Influx OSS at api.apis.guru/v2/specs/influxdata.com/2.0.0/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-07-05.