We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to the official docs from Google, the URL format should be:
POST https://pubsub.googleapis.com/v1/{topic=projects/*/topics/*}:publish
However, the publish URL being generated is missing the colon between the topic and "publish": /v1/projects/my-project-here/topics/topic-testerpublish
/v1/projects/my-project-here/topics/topic-testerpublish
It works fine though if I add a colon myself, but I doubt that's the intended way to use the library:
{-# LANGUAGE OverloadedStrings #-} import Control.Lens ((&), (.~), (<&>), (?~)) import Data.Text (Text) import Network.Google import Network.Google.PubSub import System.IO (stdout) import qualified Data.Text as Text example :: IO PublishResponse example = do lgr <- newLogger Debug stdout env <- newEnv <&> (envLogger .~ lgr) . (envScopes .~ pubSubScope) runResourceT . runGoogle env $ do send $ projectsTopicsPublish (publishRequest & prMessages .~ [pubsubMessage & pmData ?~ "Hi!"]) "projects/my-project-here/topics/topic-tester:"
The text was updated successfully, but these errors were encountered:
Looks like this is correctly fixed in develop via #34
develop
Sorry, something went wrong.
brendanhay
No branches or pull requests
According to the official docs from Google, the URL format should be:
POST https://pubsub.googleapis.com/v1/{topic=projects/*/topics/*}:publish
However, the publish URL being generated is missing the colon between the topic and "publish":
/v1/projects/my-project-here/topics/topic-testerpublish
It works fine though if I add a colon myself, but I doubt that's the intended way to use the library:
The text was updated successfully, but these errors were encountered: