Open japhar81 opened 1 month ago
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. The roadmap is driven by our customers and we have to prioritize issues that are important to them. You can influence the priority by becoming a customer. Please contact us here.
quick note: this "might" be in the images somehow? Other folks on my team see this as well, but its intermittent. Some image pulls my config works great, sometimes, not so much. Best we can tell this started a few days ago, but pinning the image version and going back a few releases doesnt seem to matter.
Hi @japhar81 thanks for reporting this.
Could you please tell me which versions you used before and which you are using now?
There has been some changes in the s3 handling back then e.g.: https://github.com/wundergraph/cosmo/releases/tag/cdn%400.10.1
Honestly not sure -- I had everything pulling latest
at the time..
Correction latest
pulled today: 1badabde0e0e
throwing that error for me
Hi @japhar81 thanks for the input.
How about the version I sent you? Is this one working as expected for you?
@AndreasZeissner intermittently, but yes..
Component(s)
controlplane
Component version
latest docker tag
wgc version
0.65.1
controlplane version
latest docker tag
router version
latest docker tag
What happened?
Description
The CDN container appears to prepend
.cosmo
to the hostname being configuredSteps to Reproduce
In docker-compose, create CDN and point to minio:
Expected Result
CDN should see the bucket -- its there, confirmed to be created by controlplane
Actual Result
Note the hostname is
cosmo.minio
. This appears nowhere in my configs, nor anywhere I can find in the cdn source code, so not sure where it's coming from.Environment information
Environment
Docker Desktop on Linux
Router configuration
Router execution config
Log output
Additional context
No response