Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

feat(appliance): version selector defaults when relreg down#64173

Merged
craigfurman merged 1 commit into
mainfrom
craig-rel-313-handle-for-releaseregistry-down-in-install-page
Jul 31, 2024
Merged

feat(appliance): version selector defaults when relreg down#64173
craigfurman merged 1 commit into
mainfrom
craig-rel-313-handle-for-releaseregistry-down-in-install-page

Conversation

@craigfurman

Copy link
Copy Markdown
Contributor

Basic fallback. See comments for a potential replacement. Even so, this gets us moving on day 0.

Closes https://linear.app/sourcegraph/issue/REL-313/handle-for-releaseregistry-down-in-install-page.

Test plan

Manual tire-kicking with pnpm run dev, and hacking the hardcoded relreg URL to be invalid.

Changelog

@craigfurman craigfurman added the no-changelog Exclude this PR from the next changelog. label Jul 31, 2024
@cla-bot cla-bot Bot added the cla-signed label Jul 31, 2024
Basic fallback. See comments for a potential replacement. Even so, this
gets us moving on day 0.
@craigfurman craigfurman force-pushed the craig-rel-313-handle-for-releaseregistry-down-in-install-page branch from b973e54 to 639a90c Compare July 31, 2024 09:19
@craigfurman craigfurman requested a review from DaedalusG July 31, 2024 15:25
@craigfurman craigfurman merged commit 45630b2 into main Jul 31, 2024
@craigfurman craigfurman deleted the craig-rel-313-handle-for-releaseregistry-down-in-install-page branch July 31, 2024 15:28
craigfurman pushed a commit that referenced this pull request Jul 31, 2024
Basic fallback. See comments for a potential replacement. Even so, this
gets us moving on day 0.

Closes
https://linear.app/sourcegraph/issue/REL-313/handle-for-releaseregistry-down-in-install-page.
// filesystem. In Kubernetes, this could be derived from a
// ConfigMap, with the files being distributed to airgap users
// out-of-band.
const publicVersions = ['v5.5.2463']

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could also maybe embed a var at build time similar to how migrator tends to handle this. Might be saying hte same thing as you though.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good idea, and isn't similar to what I was saying 😁
My comment was more speculating on how we might handle airgapped customers, since this fallback path will always be needed for them.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla-signed no-changelog Exclude this PR from the next changelog.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants