Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Fix links of github tree references #118

Merged
merged 1 commit into from
Nov 13, 2018
Merged

Fix links of github tree references #118

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/custom-gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ type GatewayConfig struct {
gatewayConfig.DispatchEvent(event []byte, src string) error
```

For detailed implementation, check out [Core Gateways](https://github.com/argoproj/argo-events/tree/eventing/gateways/core)
For detailed implementation, check out [Core Gateways](https://github.com/argoproj/argo-events/tree/master/gateways/core)

## gRPC gateway
A gRPC gateway has 3 components,
Expand All @@ -101,7 +101,7 @@ RunGateway(GatewayConfig) returns (stream Event)
The gateway processor client opens a new connection for each gateway configuration and starts listening to
events on a stream.

For detailed implementation, check out [Calendar gRPC gateway](https://github.com/argoproj/argo-events/tree/eventing/gateways/grpc/calendar)
For detailed implementation, check out [Calendar gRPC gateway](https://github.com/argoproj/argo-events/tree/master/gateways/grpc/calendar)

* To run gRPC gateway, you need to provide `rpcPort` in gateway spec.

Expand Down Expand Up @@ -136,7 +136,7 @@ List of environment variables available to user code
| GATEWAY_HTTP_CONFIG_EVENT | REST endpoint to send events to |


For detailed implementation, check out [Calendar HTTP gateway](https://github.com/argoproj/argo-events/tree/eventing/gateways/rest/calendar)
For detailed implementation, check out [Calendar HTTP gateway](https://github.com/argoproj/argo-events/tree/master/gateways/rest/calendar)

## Framework independent
The fourth option is you provide gateway implementation from scratch: watch the configuration
Expand All @@ -154,4 +154,4 @@ List of environment variables available to user code
| GATEWAY_NAME | Gateway name |

### Gateway Examples
* Example gateway definitions are available at [here](https://github.com/argoproj/argo-events/tree/eventing/examples/gateways)
* Example gateway definitions are available at [here](https://github.com/argoproj/argo-events/tree/master/examples/gateways)
2 changes: 1 addition & 1 deletion docs/gateway-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,4 +210,4 @@ Stream gateways contain a generic specification for messages received on a queue
```

### Examples
Explore [Gateway Examples](https://github.com/argoproj/argo-events/tree/eventing/examples/gateways)
Explore [Gateway Examples](https://github.com/argoproj/argo-events/tree/master/examples/gateways)
4 changes: 2 additions & 2 deletions docs/sensor-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
## Sensor Guide

Sensors define a set of dependencies (inputs) and actions (outputs). The sensor's actions will only be triggered after it's dependencies have been resolved.
[Sensor examples](https://github.com/argoproj/argo-events/tree/eventing/examples/sensors)
[Sensor examples](https://github.com/argoproj/argo-events/tree/master/examples/sensors)


### Dependencies
Expand Down Expand Up @@ -83,4 +83,4 @@ filters:
- path: bucket
type: string
value: argo-workflow-input
```
```