turbot / flowpipe-samples Goto Github PK

Flowpipe sample mods, demonstrating common pipeline patterns and how to use the Flowpipe library mods. Run directly or use as examples for your own pipelines.

Home Page: https://hub.flowpipe.io/?type=sample#search

License: Apache License 2.0

HCL 100.00%

flowpipe flowpipe-mod automation cloud devops hcl low-code orchestration security workflow

flowpipe-samples's Introduction

Flowpipe Samples

A collection of Flowpipe mods that can be used with Flowpipe.

Documentation

Mods →

Getting Started

Requirements

Each mod has its own requirements, please see the mod's README.md for any requirements, like running the Docker daemon.

Installation

Download and install Flowpipe (https://flowpipe.io/downloads). Or use Brew:

brew tap turbot/tap
brew install flowpipe

Clone:

git clone https://github.com/turbot/flowpipe-samples.git
cd flowpipe-samples

Usage

Navigate to a mod:

cd monitoring/http_list_pagination

Install mod dependencies:

flowpipe mod install

Run a pipeline:

flowpipe pipeline run http_list_pagination

Some mods require credentials and variables, please see each mod's README.md for specific instructions.

Open Source & Contributing

This repository is published under the Apache 2.0 license. Please see our code of conduct. We look forward to collaborating with you!

Flowpipe is a product produced from this open source software, exclusively by Turbot HQ, Inc. It is distributed under our commercial terms. Others are allowed to make their own distribution of the software, but cannot use any of the Turbot trademarks, cloud services, etc. You can learn more in our Open Source FAQ.

Get Involved

Join #flowpipe on Slack →

Want to help but not sure where to start? Pick up one of the help wanted issues:

flowpipe-samples's People

Contributors

Stargazers

Watchers

Forkers

tomsecurity jeromyjsmith arunvel1988

flowpipe-samples's Issues

Add new pipeline to show how to receive and handle Turbot Guardrails notifications

Is your feature request related to a problem? Please describe.
I'd like to know how to handle Guardrails notifications with a webhook trigger

Describe the solution you'd like
A new sample that demonstrates this concept

Describe alternatives you've considered
N/A

Additional context
Add any other context or screenshots about the feature request here.

Misleading error message on simple slack send

Using the example: /simple/send_slack_message results in the following error message being sent to the console in flowpipe:

➜  send_slack_message git:(main) ✗ flowpipe pipeline run send_slack_message --arg 'channel=general' --arg 'message=Hello world!'
[Execution] exec_cll6nl7a2ua5nl6un0ag
2023-12-01T18:27:16.438-0500    ERROR   Error calculating output on pipeline finish{"error": {"Detail":"output: Unsupported attribute: This object does not have an attribute named \"message\".\n(/Users/dboeke/code/flowpipe/flowpipe-samples/simple/send_slack_message/.flowpipe/mods/github.com/turbot/[email protected]/pipelines/chat/post_message.fp:59,55-63)","ID":"","Instance":"fperr_cll6nl7a2ua5nl6un0eg","Status":500,"Title":"Internal Error","Type":"error_internal","ValidationErrors":null}}

happens on rc2 and rc3
flowpipe version: Flowpipe v0.1.0-beta.202312011224

Simple slack send doesn't catch errors correctly.

Using the simple send slack sample can show that the pipeline runs correctly but in fact there was an error.

For example, if the bot user is not in a channel, the resulting server response will be:

HTTP/1.1 200 OK
date: Fri, 01 Dec 2023 23:53:42 GMT
server: Apache
vary: Accept-Encoding
x-slack-req-id: ee50ed7e8cc1e651864cfc2ebfd2c42c
x-content-type-options: nosniff
x-xss-protection: 0
pragma: no-cache
cache-control: private, no-cache, no-store, must-revalidate
expires: Sat, 26 Jul 1997 05:00:00 GMT
content-type: application/json; charset=utf-8
x-accepted-oauth-scopes: chat:write
x-oauth-scopes: incoming-webhook,chat:write
access-control-expose-headers: x-slack-req-id, retry-after
access-control-allow-headers: slack-route, x-slack-version-ts, x-b3-traceid, x-b3-spanid, x-b3-parentspanid, x-b3-sampled, x-b3-flags
strict-transport-security: max-age=31536000; includeSubDomains; preload
referrer-policy: no-referrer
x-slack-unique-id: ZWpyBqJuBvu36zty5HG9CQAAADc
x-slack-backend: r
access-control-allow-origin: *
content-length: 37
via: 1.1 slack-prod.tinyspeck.com, envoy-www-iad-pndeswgp, envoy-edge-iad-hrqnjmyt
x-envoy-attempt-count: 1
x-envoy-upstream-service-time: 24
x-backend: main_normal main_canary_with_overflow main_control_with_overflow
x-server: slack-www-hhvm-main-iad-aafl
x-slack-shared-secret-outcome: no-match
x-edge-backend: envoy-www
x-slack-edge-shared-secret-outcome: no-match
connection: close

{
  "ok": false,
  "error": "not_in_channel"
}

notice that "ok" is false and the associated error message.