chore: move region_config.json to configmap #621
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Your org requires the Graphite merge queue for merging into mainYou must have a Graphite account in order to use the merge queue. Sign up using this link. You can enable merging using labels in your Graphite merge queue settings. |
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @NathanFlurry and the rest of your teammates on |
MasterPtato
approved these changes
Apr 1, 2024
Contributor
Merge activity
|
Previously, the region_config.json file that's included with `include_bytes!` might be incorreclty cached and deployed to the wrong cluster in Bolt.
NathanFlurry
force-pushed
the
03-31-chore_move_region_config.json_to_configmap
branch
from
3bbdad7 to
49e439e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the region_config.json file that's included with
include_bytes!might be incorreclty cached and deployed to the wrong cluster in Bolt.