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

Review example configs and documentation to make it more clear that topicPrefix v02.post is needed to subscribe to our public brokers #961

Closed
reidsunderland opened this issue Mar 8, 2024 · 2 comments
Labels
Discussion_Needed developers should discuss this issue. Documentation Primary deliverable of this item is documentation enhancement New feature or request good first issue Good for newcomers

Comments

@reidsunderland
Copy link
Member

reidsunderland commented Mar 8, 2024

(I created this without a description because I wanted to get the issue number for to email to the client).

I'm not sure if they created the config on their own or found an old example somewhere. But it didn't have topicPrefix v02.post so it didn't work. When I tested it, I had topicPrefix v02.post in my default.conf, so it worked for me.

Alternatively, we could set up shovels and start publishing v03 messages as well?

@reidsunderland reidsunderland added enhancement New feature or request good first issue Good for newcomers Documentation Primary deliverable of this item is documentation Discussion_Needed developers should discuss this issue. labels Mar 8, 2024
@petersilva
Copy link
Contributor

yeah.... hard to figure out how to make that move obvious/clear...

fwiw... all the examples include it. e.g:


sr3 list examples
sr3 add subscribe/dd_amis.conf

reidsunderland added a commit that referenced this issue Mar 8, 2024
@reidsunderland
Copy link
Member Author

The client provided links to the documents they were reading:

I added topicPrefix v02.post where it was needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion_Needed developers should discuss this issue. Documentation Primary deliverable of this item is documentation enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants