We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Just follow the exact steps in Argo Events tutorial section 'Trigger Template Parameterization' at https://argoproj.github.io/argo-events/tutorials/02-parameterization/, and always getting 'hello world' output, instead of expected output of 'amazing!!'
To Reproduce Steps to reproduce the behavior: Just follow the exact steps in Argo Events tutorial section 'Trigger Template Parameterization' at https://argoproj.github.io/argo-events/tutorials/02-parameterization/
Expected behavior Should have got expected output of 'amazing!!', but got 'hello world' output
Someone else already mentioned the same here: #3161.
If argo events no longer supports this use case, please remove this misleading section in the tutorial.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Just follow the exact steps in Argo Events tutorial section 'Trigger Template Parameterization' at https://argoproj.github.io/argo-events/tutorials/02-parameterization/, and always getting 'hello world' output, instead of expected output of 'amazing!!'
To Reproduce
Steps to reproduce the behavior:
Just follow the exact steps in Argo Events tutorial section 'Trigger Template Parameterization' at https://argoproj.github.io/argo-events/tutorials/02-parameterization/
Expected behavior
Should have got expected output of 'amazing!!', but got 'hello world' output
Someone else already mentioned the same here: #3161.
If argo events no longer supports this use case, please remove this misleading section in the tutorial.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: