Skip to content

feat: Update v26.1 docs to explain Studios is enabled on all ws by default #1105

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.

Sign up for GitHub

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

Merged
bebosudo merged 23 commits into from
Feb 6, 2026
Merged

feat: Update v26.1 docs to explain Studios is enabled on all ws by default #1105

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
c2c8a53
Add Pipeline Optimization and Studios helm docs in ent vNext
bebosudo Jan 30, 2026
4acfd69
Move generic Studios instructions to install-studios page, keep k8s a…
bebosudo Feb 2, 2026
08b6bda
Update ingress mention and warning, make it more cloud-agnostic
bebosudo Feb 2, 2026
7e5ee3d
Fix sidebar
bebosudo Feb 2, 2026
78422c5
Backport studios and groundswell helm + docs reorg to v25.3
bebosudo Feb 2, 2026
58943e7
Fix sidebars for v25.x
bebosudo Feb 3, 2026
581070c
Consolidate product requirements in each /install-* page
bebosudo Feb 3, 2026
188f182
Backport changes to v25.x
bebosudo Feb 3, 2026
24ed648
Fix link after /enterprise/studios was removed
bebosudo Feb 3, 2026
e53f4ea
Fix some more links
bebosudo Feb 3, 2026
516fb3c
Fix more links
bebosudo Feb 3, 2026
951fc48
Fix codeowners to use the new links /enterprise/*-kubernetes and -helm
bebosudo Feb 3, 2026
38bd386
Update changelogs with new links
bebosudo Feb 3, 2026
233c2b3
Update homepage link to install studios enterprise
bebosudo Feb 3, 2026
9a23270
Fix broken Studios links in v25.3 configuration files
justinegeffen Feb 4, 2026
1ecd21d
Fix broken Studios links in v25.1 and v25.2 configuration files
justinegeffen Feb 4, 2026
c8b0d8e
Update vNext too
bebosudo Feb 4, 2026
24ea571
Fix ../ in data_features_env.yml
bebosudo Feb 4, 2026
f7f802d
Merge branch 'master' into chiusole/add-studios-and-pipeline-optimiza…
justinegeffen Feb 5, 2026
2cd2e1a
Update v26.1 docs to explain Studios is enabled on all ws by default …
bebosudo Feb 5, 2026
b54074c
Removed mention of tower.yml entirely to control studios in v26.1
bebosudo Feb 6, 2026
3f3cdc4
Merge branch 'master' into chiusole/update-v26.1-with-studios-on-by-d…
bebosudo Feb 6, 2026
7769f68
Remove mentions of tower.yml from k8s/compose guides for studios in p…
bebosudo Feb 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 1 addition & 15 deletions platform-enterprise_docs/enterprise/install-studios.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,21 +45,7 @@ Studios uses the following set of domains and subdomains:

## Studios workspace availability

You can configure which organizational workspaces have access to Studios. This configuration is set in the `tower.yml` file. The `tower.data-studio.allowed-workspaces` field supports the following options:

- `allowed-workspaces: []`: Disables Studios. This is the default if the `allowed-workspaces` field is not specified.
- `allowed-workspaces: [ <WORKSPACE_ID>,<WORKSPACE_ID> ]`: Enables Studios for the comma-separated list of organizational workspace IDs.
- `allowed-workspaces: null`: Enables Studios for all organizational workspaces.

In the Platform Helm chart, set the desired configuration in the `platform.YAMLConfigFileContent` field. For example, to enable Studios for workspaces 12345 and 67890:

```yaml
platform:
YAMLConfigFileContent: |-
tower:
data-studio:
allowed-workspaces: [12345,67890]
```
You can configure which organizational workspaces have access to Studios by setting the `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` environment variable on the backend containers. By default, all workspaces have access to Studios. To restrict access to specific workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` to a comma-separated list of workspace names. For example, `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES="12345,67890"` allows only the workspaces named `12345` and `67890` to access Studios. To disable access to Studios for all workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES=""` (an empty string).

## Available Studios environment images

Expand Down
16 changes: 1 addition & 15 deletions platform-enterprise_docs/enterprise/studios-docker-compose.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,21 +60,7 @@ Other than the basic requirements [already listed in the Studios installation ov
- `TOWER_OIDC_REGISTRATION_INITIAL_ACCESS_TOKEN`: The same value as `oidc_registration_token`.
- `TOWER_OIDC_PEM_PATH`: The file path to the PEM certificate (e.g., `/data-studios-rsa.pem`).

1. Edit the `tower.yml` file and include the following snippet to enable Studios in all workspaces in your Platform instance:

```yaml
tower:
data-studio:
allowed-workspaces: null
```

Alternatively, you can specify a comma-separated list of workspace IDs to enable Studios only on those workspaces.

```yaml
tower:
data-studio:
allowed-workspaces: [12345,67890]
```
1. From Platform v26.1, Studios is enabled by default on all workspaces. To enable Studios on specific workspaces only, set the `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` environment variable (e.g., `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES="12345,67890"`) on the Platform backend containers. To disable Studios for all workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES=""` (an empty string).
Copy link
Member

@gwright99 gwright99 Feb 6, 2026

Choose a reason for hiding this comment

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

Both of these approaches work, so I'm not necessarily complaining. But what's the point of moving away from tower.yml in favour of the environment variable way (particularly since previous docs referenced tower.yml)?

Is the intention to do this across all configurations? (i.e deprecate and eventually remove tower.yml as a configuration method)?


1. Start your Platform instance:

Expand Down
18 changes: 1 addition & 17 deletions platform-enterprise_docs/enterprise/studios-kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,23 +102,7 @@ You can also check the current template configuration using `https://towerurl/ap
- `TOWER_DATA_STUDIO_CONNECT_URL`: The URL of the Studios connect proxy, such as `https://connect.example.com/`.
- `TOWER_OIDC_REGISTRATION_INITIAL_ACCESS_TOKEN`: The same value as the `oidc_registration_token` value created previously.

1. Edit the ConfigMap named `tower-yml` in the `configmap.yml` and include the following snippet:

```yaml
data:
tower.yml: |-
tower:
data-studio:
allowed-workspaces: null
```

Alternatively, you can specify a comma-separated list of workspace IDs to enable Studios only on those workspaces.

```yaml
tower:
data-studio:
allowed-workspaces: [12345,67890]
```
1. From Platform v26.1, Studios is enabled by default on all workspaces. To enable Studios on specific workspaces only, set the `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` environment variable (e.g., `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES="12345,67890"`) on the Platform backend containers. To disable Studios for all workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES=""` (an empty string).

1. Apply the updated configuration:

Expand Down