Skip to content

Hitting "During Config validation provided topology is either non existing or does not end with .yaml occurred" #181

Answered by Templum
A586788 asked this question in Q&A
Discussion options

You must be logged in to vote

Generally speaking, this issue is quite simple, either you don't provide any correct absolute path (which is not the case). Or it seems to be more likely the path provided is not available in the running instance.

So in your situation, I would attempt to verify that the folder you try to access does really exist in the running instance. Because from what you shared it is not visible to me how you pass in the topology.yaml, something that was discussed in great length here.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@A586788
Comment options

Answer selected by A586788
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants