Solution skill
Mezmo Terraform provider: HTTP shared_source does not export endpoint
Complete solution
Shows how to fix mezmo Terraform provider: HTTP shared_source does not export endpoint. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Upgrade the provider to v4.2.0 or later and read the endpoint from the new consumer_id attribute instead of copying it by hand. They added that attribute in PR #214, and it shipped in provider v4.2.0.
Steps
- What was going on
They were splitting one complex Mezmo pipeline into several pipelines sharing a single HTTP sharedsource. With single HTTP sources they could build the endpoint URL for their log forwarder from the pipeline ID, but the sharedsource's ID is not the value that ends up in the final shared-source endpoint. Nothing in Terraform state exposed the endpoint either, so they had to create the shared source and then manually copy the endpoint URL into the log forwarder. They asked whether any Terraform attribute could give them the endpoint dynamically.
- What fixed it
A Mezmo maintainer confirmed this was an oversight on their side: the ID that can be used to derive the shared-source endpoint is the consumerid. They added that attribute in PR #214, and it shipped in provider v4.2.0. Upgrade the provider to v4.2.0 or later and read the endpoint from the new consumerid attribute instead of copying it by hand.
Expected: What fixed it A Mezmo maintainer confirmed this was an oversight on their side: the ID that can be used to derive the shared-source endpoint is the consumer_id.
When to use
You are seeing this: What was going on They were splitting one complex Mezmo pipeline into several pipelines sharing a single HTTP sharedsource. Use this skill when you run into "Mezmo Terraform provider: HTTP sharedsource does not export endpoint".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: provider v4.2.0. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In the thread, the question was: They were splitting one complex Mezmo pipeline into several pipelines sharing a single HTTP sharedsource. With single HTTP sources they could build the endpoint URL for their log forwarder from the pipeline ID, but the sharedsource's ID is not the value that ends up in the final shared-source endpoint. Nothing in Terraform state exposed the endpoint either, so they had to create the shared source and then manually copy the endpoint URL into the log forwarder. They asked whether any Terraform attribute could give them the endpoint dynamically. The verified resolution: A Mezmo maintainer confirmed this was an oversight on their side: the ID that can be used to derive the shared-source endpoint is the consumerid. They added that attribute in PR #214, and it shipped in provider v4.2.0. Upgrade the provider to v4.2.0 or later and read the endpoint from the new consumerid attribute instead of copying it by hand. Thread: https://vectle.com/threads/thr_EgkYOEC8IVXUphXje8WMbw
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_kf9WLAG6b-1EW85H3Wn7zQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Mezmo Terraform provider: HTTP shared_source does not export endpoint <span>— Vectle</span></a>