🌱 Add catalogd metas service demo

[grokspawn]

Resolves demo items of #1783

Description

• adds a demo for the metas catalog service endpoint (but does not make this part of regular CI, since it is currently dependent on deploying from local artifacts
• Fixes a bug in the Makefile where the VERSION attribute would be empty instead of undefined, and succeeds now only with valid (non-empty) input

Demo

Reviewer Checklist

• API Go Documentation
• Tests: Unit Tests (and E2E Tests, if appropriate)
• Comprehensive Commit Messages
• Links to related GitHub Issue(s)

[netlify]

✅ Deploy Preview for olmv1 ready!

Name	Link
🔨 Latest commit	0303310
🔍 Latest deploy log	https://app.netlify.com/sites/olmv1/deploys/67c9e2bf50e59b0008862180
😎 Deploy Preview	https://deploy-preview-1840--olmv1.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.39%. Comparing base (e4e76d2) to head (0303310).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1840   +/-   ##
=======================================
  Coverage   68.39%   68.39%           
=======================================
  Files          63       63           
  Lines        5136     5136           
=======================================
  Hits         3513     3513           
  Misses       1392     1392           
  Partials      231      231           

Flag	Coverage Δ
e2e	51.52% <ø> (ø)
unit	56.01% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tmshort]

Why are some of these "double" commented?

[grokspawn]

The linter said "use single quotes so they are not expanded now, but are expanded later", and the general syntax is "quote to capture strings with spaces / special characters".

[grokspawn]

This is not OK. The problem here appears to be that catalogd's deployment conditions are serving := True with progressing := True... but the api is not actually serving.

I need to diagnose this more, but it looks like an architectural communications gap rather than a bug.

[perdasilva]

This is not OK. The problem here appears to be that catalogd's deployment conditions are serving := True with progressing := True... but the api is not actually serving.

I need to diagnose this more, but it looks like an architectural communications gap rather than a bug.

should we hold until this is resolved? Or can we still merge and resolve out of band?

[grokspawn]

This is not OK. The problem here appears to be that catalogd's deployment conditions are serving := True with progressing := True... but the api is not actually serving.
I need to diagnose this more, but it looks like an architectural communications gap rather than a bug.

should we hold until this is resolved? Or can we still merge and resolve out of band?

IMO we can merge this and then look into what's going on with catd under the hood. It doesn't look like a demo bug, but the demo could be useful in diagnosing what's going on in catd.

[Edit: Dialoguing elsewhere we reached consensus that .status communicates kube status only, and that clients of any endpoint need to handle error conditions on endpoints. I updated the script to retry on 404 and now it runs much more quickly!]

[perdasilva]

lgtm ^^ thanks for adding the curl retries =D

[perdasilva]

we should probably standardize the w:h for the demo window when generating it, if that's possible. Nothing that needs doing in the PR tho...