-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Require env var for custom git fetch #39630
Conversation
Thanks @andreeleuterio for proposing to move it to a file! Makes things a lot easier. |
Codenotify: Notifying subscribers in CODENOTIFY files for diff 91e8afb...b07359b.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks and LGTM other than some world-class formatting issues 😛
Co-authored-by: Joe Chen <joe@sourcegraph.com>
Co-authored-by: Joe Chen <joe@sourcegraph.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming the CUSTOM_GIT_FETCH_CONF env var is to be set on the sourcegraph-frontend deployment? Does this env var need to be set on any other deployments?
Should be set on all |
Co-authored-by: Joe Chen <joe@sourcegraph.com>
@evict @andreeleuterio Is there a reason we moved this to a file? It seems simpler to keep the config in the site-config and leverage an infrastructure-level config option to tune it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Holding this till we can provide easy instructions of how to mount the config file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the original motivation for this? TBH what we are doing now is just more clunky and lives outside of things like being able to use the migrator/etc for it.
Generally when deprecating something we give a release or two before making it non functional.
Co-authored-by: Keegan Carruthers-Smith <keegan.csmith@gmail.com>
@keegancsmith you can find more context here. tl;dr is that this can't be a site-admin setting in the context of Managed Instances. |
schema/site.schema.json
Outdated
@@ -303,11 +303,11 @@ | |||
} | |||
}, | |||
"customGitFetch": { | |||
"description": "JSON array of configuration that maps from Git clone URL domain/path to custom git fetch command.", | |||
"description": "DEPRECATED: THIS VALUE WILL IS IGNORED. CONFIGURATION MOVED TO A LOCAL FILE USE ENVIRONMENT VARIABLE `CUSTOM_GIT_FETCH_CONF` TO SET FILE PATH. JSON array of configuration that maps from Git clone URL domain/path to custom git fetch command.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "DEPRECATED: THIS VALUE WILL IS IGNORED. CONFIGURATION MOVED TO A LOCAL FILE USE ENVIRONMENT VARIABLE `CUSTOM_GIT_FETCH_CONF` TO SET FILE PATH. JSON array of configuration that maps from Git clone URL domain/path to custom git fetch command.", | |
"description": "DEPRECATED: THIS VALUE IS IGNORED. CONFIGURATION MOVED TO A LOCAL FILE USE ENVIRONMENT VARIABLE `CUSTOM_GIT_FETCH_CONF` TO SET FILE PATH. JSON array of configuration that maps from Git clone URL domain/path to custom git fetch command.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we still read this value if the envvar is not set for 2 releases just so we don't break the customers we know use this? Additionally I'd document that the envvar needs to be set on the gitserver container.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please provide feedback on this new PR #42704
Co-authored-by: Ryan Slade <ryanslade@gmail.com>
Closing this MR in favour of a simpler solution: #42704. This makes sure the customer can keep using it while others have the option of disabling it. |
Move
customGitFetch
configuration from site-admin to a local file.Test plan
Manual review
Manual testing