Skip to content
New issue

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

edge-controller: configure primary site mode through values #101

Merged
merged 2 commits into from
Nov 12, 2024

Conversation

james-rms
Copy link
Contributor

@james-rms james-rms commented Nov 11, 2024

Changelog

  • Added: expose primary site configuration for edge controller through helm chart values.

Docs

https://github.com/foxglove/docs/pull/481

Description

It's possible to use an edge controller with a hosted primary site, but right now users don't have a good way to configure that. This PR plumbs through a configuration variable for this.

@james-rms james-rms force-pushed the jrms/edge-set-primary-site-mode branch from c2a9930 to 46daf44 Compare November 11, 2024 04:49
@james-rms james-rms force-pushed the jrms/edge-set-primary-site-mode branch from 46daf44 to 40fb64a Compare November 11, 2024 04:50
@james-rms james-rms requested review from bryfox and sofuture November 12, 2024 20:16
# Values: "self-managed", "hosted"
primarySiteMode: self-managed
# The cloud provider where the self-managed primary site inbox bucket lives.
# If `primarySiteMode` is set to `hosted`, these values are ignored.
Copy link
Contributor

Choose a reason for hiding this comment

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

It might be worth saying "this value" is ignored, and repeating it for the bucket name below... for clarity and future-proofing.

@james-rms james-rms merged commit c19a5fa into main Nov 12, 2024
1 check passed
@james-rms james-rms deleted the jrms/edge-set-primary-site-mode branch November 12, 2024 23:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants