You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
From what I understand from the documentation: I've deployed argo-events (clusterScope), eventbus, eventsource and sensor for BitbucketCloud with Basic Auth. The Bitbucket Webhook is generated when the eventSource is deployed, but I have no visibility of the token.
I manage to trigger a Workflow that calls a WorkflowTemplate, but the payload retrieved is not usable. Isn't there a problem with the token?
Did i miss something ?
To Reproduce
Steps to reproduce the behavior:
Deploy argo-events with helm, clusterScoped
Deploy the EventBus (default exampleà
Deploy the eventSource (on bitbucket Cloud, a new Webhook is automatically created)
Deploy the sensor
Call the / to trigger the Workflow.
Here is the example Sensor to get the payload json data :
This issue has been automatically marked as stale because it has not had
any activity in the last 60 days. It will be closed if no further activity
occurs. Thank you for your contributions.
Describe the bug
From what I understand from the documentation: I've deployed argo-events (clusterScope), eventbus, eventsource and sensor for BitbucketCloud with Basic Auth. The Bitbucket Webhook is generated when the eventSource is deployed, but I have no visibility of the token.
I manage to trigger a Workflow that calls a WorkflowTemplate, but the payload retrieved is not usable. Isn't there a problem with the token?
Did i miss something ?
To Reproduce
Steps to reproduce the behavior:
Here is the example Sensor to get the payload json data :
Expected behavior
I should get the json bitbucket payload (like this one repo:push) but i got something not human readable (see above screenshot)
Screenshots
Log from the sensor :
Webhook successfully called on bitbucket :
Environment (please complete the following information):
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: