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.

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

Fail on startup when sources and targets aren't reachable #151

Open
colmsnowplow opened this issue Jun 23, 2022 · 0 comments
Open

Fail on startup when sources and targets aren't reachable #151

colmsnowplow opened this issue Jun 23, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@colmsnowplow
Copy link
Collaborator

When provided with the correct set of env vars for authentication, the EventHub target will create a client.

However, it currently doesn't ping the endpoint or check that it can connect - so if the credentials themselves are invalid, we don't find out until we send some actual data.

It will be easier to manage deployments if the app fails on startup in this scenario - indeed some of the targets will do so. We should:

a) Verify what the behaviour is for all targets
b) For those targets whose clients don't do so already, instrument some behaviour to check the connection at creation of target
c) Do the same for the sources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants