You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/admin/executors/deploy_executors_kubernetes.mdx
+44-3Lines changed: 44 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,48 @@ Executors interact with the Kubernetes API to manage the lifecycle of individual
13
13
|`batch`|`jobs`|`create`, `delete`| Executors create Job pods to run processes. Once Jobs are completed, they are cleaned up. |
14
14
||`pods`, `pods/log`|`get`, `list`, `watch`| Executors need to look up and steam logs from the Job Pods. |
15
15
16
-
See the [example Role YAML](https://sourcegraph.com/github.com/sourcegraph/sourcegraph@main/-/blob/cmd/executor/kubernetes/batches/executor-batches.Role.yml) for more details on the exact RBAC requirements for native Kubernetes Executors.
16
+
Here's an example Role YAML to demonstrate the RBAC requirements for native Kubernetes Executors:
17
+
18
+
```yaml
19
+
apiVersion: rbac.authorization.k8s.io/v1
20
+
kind: Role
21
+
metadata:
22
+
name: sg-executor-batches-role
23
+
namespace: default
24
+
rules:
25
+
- apiGroups:
26
+
- batch
27
+
resources:
28
+
- jobs
29
+
verbs:
30
+
- create
31
+
- delete
32
+
- apiGroups:
33
+
- ""
34
+
resources:
35
+
- pods
36
+
- pods/log
37
+
verbs:
38
+
- get
39
+
- list
40
+
- watch
41
+
# Secrets are required post 5.5, when all pods run a single job
42
+
- apiGroups:
43
+
- ""
44
+
resources:
45
+
- secrets
46
+
verbs:
47
+
- create
48
+
- delete
49
+
# PVCs are required if KUBERNETES_JOB_VOLUME_TYPE is "pvc"
50
+
# - apiGroups:
51
+
# - ""
52
+
# resources:
53
+
# - persistentvolumeclaims
54
+
# verbs:
55
+
# - create
56
+
# - delete
57
+
```
17
58
18
59
## Deployment
19
60
@@ -94,5 +135,5 @@ The Executor Docker image is available on Docker Hub at [`sourcegraph/executor-k
94
135
### Example Configuration YAML
95
136
96
137
See
97
-
the [local development YAMLs](https://sourcegraph.com/github.com/sourcegraph/sourcegraph@main/-/blob/cmd/executor/kubernetes)
98
-
for an example of how to configure the Executor in Kubernetes.
138
+
the [local development YAMLs](https://sourcegraph.com/github.com/sourcegraph/sourcegraph-public-snapshot@main/-/blob/cmd/executor/kubernetes)
139
+
for an example of how to configure the Executor in Kubernetes.
It's also possible to use other methods to get permission data from a code host into the Sourcegraph instance.
50
52
@@ -61,16 +63,18 @@ To know more about each method that we support, please follow the link above.
61
63
## Supported code hosts
62
64
63
65
Support for repository permissions accross different code hosts is different. The following table captures current state of support (ordered alphabetically):
64
-
| Code host |[Permission Syncing](/admin/permissions/syncing)|[Webhooks for Permissions](/admin/permissions/webhooks)|[Explicit API](/admin/permissions/api)|[Scale supported](#supported-scale)|
Copy file name to clipboardExpand all lines: docs/admin/updates/automatic.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Automatic multi-version upgrades
2
2
3
-
> Warning: Automatic upgrades to v5.10.0 will fail please upgrade to a v5.9.x version and perform a standard upgrade instead! See our [postgres 12 end of life](https://sourcegraph.com/docs/admin/postgres12_end_of_life_notice#postgres-12-end-of-life) notice!
3
+
> Warning: Automatic upgrades to v5.10.0 will fail please upgrade to a v5.9.x version and perform a standard upgrade instead! See our [postgres 12 end of life](https://sourcegraph.com/docs/admin/postgres12_end_of_life_notice#postgres-12-end-of-life) notice! This is one of the reasons the "Auto Upgrade" toggle is automatically turned off after a version change. This behavior is intentional—it’s designed to prevent users from unintentionally performing multi-version upgrades (MVUs) that span critical changes, such as major infrastructure updates like a PostgreSQL version upgrade.
4
4
5
5
From **Sourcegraph 5.1 and later**, multi-version upgrades can be performed **automatically** as if they were a standard upgrade for the same deployment type. Automatic multi-version upgrades take the following general form:
Copy file name to clipboardExpand all lines: docs/code-search/code-navigation/precise_code_navigation.mdx
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Precise code navigation relies on the open source [SCIP Code Intelligence Protoc
22
22
23
23
## Setting up code navigation for your codebase
24
24
25
-
<Callouttype="info">There are several options for setting up precise code navigation listed below. However, we always recommend you start by manually indexing your repo locally using the [approriate indexer](/code-navigation/writing_an_indexer#quick-reference) for your language. Code and build systems can vary by project and ensuring you can first succesfully run the indexer locally leads to a smoother experience since it is vastly easier to debug and iterate on any issues locally before trying to do so in CI/CD or in Auto-Indexing.</Callout>
25
+
<Callouttype="info">There are several options for setting up precise code navigation listed below. However, we always recommend you start by manually indexing your repo locally using the [approriate indexer](/code-search/code-navigation/writing_an_indexer#quick-reference) for your language. Code and build systems can vary by project and ensuring you can first succesfully run the indexer locally leads to a smoother experience since it is vastly easier to debug and iterate on any issues locally before trying to do so in CI/CD or in Auto-Indexing.</Callout>
26
26
27
27
1.**Manual indexing**. Index a repository and upload it to your Sourcegraph instance:
28
28
@@ -32,12 +32,8 @@ Precise code navigation relies on the open source [SCIP Code Intelligence Protoc
32
32
-[Index a Python repository](https://sourcegraph.com/github.com/sourcegraph/scip-python)
33
33
-[Index a Ruby repository](https://sourcegraph.com/github.com/sourcegraph/scip-ruby)
34
34
35
-
2.[**Automate indexing via CI**](/code_navigation/how-to/adding_scip_to_workflows): Add indexing and uploading to your CI setup.
35
+
2.[**Automate indexing via CI**](/code-search/code-navigation/how-to/adding_scip_to_workflows): Add indexing and uploading to your CI setup.
36
36
3.[**Auto-indexing**](/code-search/code-navigation/auto_indexing#enable-auto-indexing): Sourcegraph will automatically index your repositories and enable precise code navigation for them.
37
-
4. Set up **auto-dependency indexing** to navigate and search through the dependencies your code uses:
38
-
-**Go**: Enable [auto-indexing](/code-search/code-navigation/auto_indexing) and Sourcegraph will start indexing your dependencies.
39
-
-**JavaScript, TypeScript**: Enable [auto-indexing](/code-search/code-navigation/auto_indexing#enable-auto-indexing) and set up an [npm dependencies code host](/integration/npm).
40
-
-**Java, Scala, Kotlin**: Enable [auto-indexing](/code-search/code-navigation/auto_indexing) and set up a [JVM dependencies code host](/integration/jvm).
Copy file name to clipboardExpand all lines: docs/cody/prompts-guide.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -270,7 +270,7 @@ This prompt can help you if you want to generate unit tests for your code based
270
270
271
271
>You're working with Golang and need Cody to generate unit tests that comply with your team’s conventions. Your organization follows a specific structure for tests, including table-driven tests and `require` from the `testify` package for assertions. However, Cody might provide a simple test that does not align with your standards.
272
272
273
-
While you can use the default `generate-unit-tests` prompt but to get the desired output, you can customize e the prompt to include the following:
273
+
While you can use the default `generate-unit-tests` prompt but to get the desired output, you can customize the prompt to include the following:
274
274
275
275
```
276
276
Please generate Golang unit tests that adhere to the following conventions:
0 commit comments