Skip to content

Conversation

@michalbiesek
Copy link
Contributor

No description provided.

@michalbiesek michalbiesek linked an issue Jul 20, 2023 that may be closed by this pull request
@michalbiesek michalbiesek force-pushed the feat-1594-payload-via-event branch 3 times, most recently from 95ba0fe to 697899b Compare July 20, 2023 11:51
@michalbiesek michalbiesek force-pushed the feat-1594-payload-via-event branch 9 times, most recently from c0ab39f to ed3bb7f Compare July 21, 2023 20:17
- allows to change payload destination to event transport
- by default the payloads will go to directory
- it is possible to change this behaviour via:
  - `--payloadsdest` argument in `scope` CLI
  - `SCOPE_PAYLOAD_DEST` environment variable
  - allowed values are for the above are "event", "dir"

Closes #1594
@michalbiesek michalbiesek force-pushed the feat-1594-payload-via-event branch from ed3bb7f to 605b55d Compare July 21, 2023 20:28
@michalbiesek michalbiesek changed the title Add support for payload via event transport [HOLD] Add support for payload via event transport Jul 24, 2023
@michalbiesek michalbiesek marked this pull request as draft July 24, 2023 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for sending the payloads using event channel

2 participants