ISSUE
The guidance provided within the file located here will not run as is currently documented. https://github.com/treasure-data/treasure-boxes/tree/6812e5ed4b67a8eeea3e93e731d35abaa3552c7b/scenarios/kick_another_account_workflow_kohki
In addition, I feel this example unnecessarily duplicates the guidance provided here, which I have confirmed to work. https://github.com/treasure-data/treasure-boxes/blob/a7eb9a6416a71d4e0af8e6a9a2f5ed2a49d7961f/tool-box/trigger-another-workflow/trigger.dig
It is also somewhat concerning that the commentary from 2019 recommends that this NOT be utilized...however, as a means of writing DRY (DO NOT REPEAT YOURSELF) code, this is a great way to create sub routines, especially at a DEV or QA level, and then reuse them where applicable.
EXPECTED RESULT
There would be a single source of guidance for this objective, with additional commentary, examples and / or flows referenced in the single README.md and related examples
ISSUE
The guidance provided within the file located here will not run as is currently documented. https://github.com/treasure-data/treasure-boxes/tree/6812e5ed4b67a8eeea3e93e731d35abaa3552c7b/scenarios/kick_another_account_workflow_kohki
In addition, I feel this example unnecessarily duplicates the guidance provided here, which I have confirmed to work. https://github.com/treasure-data/treasure-boxes/blob/a7eb9a6416a71d4e0af8e6a9a2f5ed2a49d7961f/tool-box/trigger-another-workflow/trigger.dig
It is also somewhat concerning that the commentary from 2019 recommends that this NOT be utilized...however, as a means of writing DRY (DO NOT REPEAT YOURSELF) code, this is a great way to create sub routines, especially at a DEV or QA level, and then reuse them where applicable.
EXPECTED RESULT
There would be a single source of guidance for this objective, with additional commentary, examples and / or flows referenced in the single README.md and related examples