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
|`INFRAHUB_SECURITY_RESTRICT_UNTRUSTED_JINJA2_FILTERS`| Indicates if untrusted Jinja2 filters should be disallowed for computed attributes | boolean | True |
192
192
|`INFRAHUB_SECURITY_SSO_USER_DEFAULT_GROUP`| Name of the group to which users authenticated via SSO will belong if not provided by identity provider | None | None |
|`INFRAHUB_OAUTH2_GOOGLE_DISPLAY_LABEL`| None | string | Google |
207
+
|`INFRAHUB_OAUTH2_GOOGLE_FETCH_GROUPS`| Whether to use Cloud Identity API to fetch user groups. Note: requires additional scopes: https://www.googleapis.com/auth/cloud-identity.groups.readonly| boolean | False |
208
+
|`INFRAHUB_OAUTH2_GOOGLE_CLOUDIDENTITY_URL`| Google Cloud endpoint for Cloud Identity. Using searchDirectGroups by default because it is available for the Free plan | string |https://cloudidentity.googleapis.com/v1/groups/-/memberships:searchDirectGroups|
|`INFRAHUB_OIDC_GOOGLE_FETCH_GROUPS`| Whether to use Cloud Identity API to fetch user groups. Note: requires additional scope: https://www.googleapis.com/auth/cloud-identity.groups.readonly| boolean | False |
240
+
|`INFRAHUB_OIDC_GOOGLE_CLOUDIDENTITY_URL`| Google Cloud endpoint for Cloud Identity. Using searchDirectGroups by default because it is available for the Free plan | string |https://cloudidentity.googleapis.com/v1/groups/-/memberships:searchDirectGroups|
Infrahub provides an interface to store and retrieve files or objects in an object-storage. The object-storage is used internally within Infrahub to store rendered artifacts, but it can be used to store any textbased file or content.
7
+
Infrahub provides an interface to store and retrieve files or objects in objectstorage. Object storage is used internally within Infrahub to store rendered artifacts, but you can also use it to store any text-based file or content.
8
8
9
-
You can interface with the object-storage through the REST API and Python SDK.
10
-
See the [object-storage guide](../guides/object-storage) and [object-storage Python SDK]($(base_url)python-sdk/guides/object-storage) guide for more information.
9
+
You can interact with object storage through the REST API and Python SDK. For practical steps, see the [object storage guide](../guides/object-storage) and the [object storage Python SDK guide]($(base_url)python-sdk/guides/object-storage).
11
10
12
-
## Supported backends
11
+
## Supported storage backends
13
12
14
-
At this moment Infrahub supports using local storage, or AWS S3 storage backends. Support for other storage backends will be added in the future.
13
+
Infrahub supports two storagebackends:
15
14
16
-
### Local storage
15
+
- Local storage (configured by default)
16
+
- AWS S3 (or S3-compatible) storage
17
+
18
+
You configure the backend by setting the appropriate environment variables. These variables are typically set in your Docker Compose YAML file or in the deployment environment for your containers. See the [Infrahub configuration reference](../reference/configuration.mdx) for a full list of options.
19
+
20
+
---
17
21
18
-
Infrahub can use local storage as a storage backend. It can be any directory on a filesystem that is attached to the system on which Infrahub runs. The only requirement is that all the Infrahub API servers and Task workers need access to the filesystem.
22
+
### Local storage
19
23
20
-
To setup Infrahub to use local storage backend you can use the following configuration:
24
+
By default, Infrahub uses local storage for artifacts and files. No additional configuration is required unless you want to change the storage location.
21
25
22
-
```toml
23
-
[storage]
24
-
driver = "local"
26
+
To explicitly configure local storage, set the following environment variables in your Docker Compose YAML file or deployment environment:
For all available configuration options and environment variables, refer to the [Infrahub configuration reference](../reference/configuration.mdx#infrahub_storage_s3).
35
54
36
-
To setup Infrahub to use AWS S3 as a storage backend you can use the following configuration:
55
+
---
37
56
38
-
```toml
39
-
[storage]
40
-
driver = "s3"
57
+
:::info
58
+
You can switch between storage backends by changing the value of `INFRAHUB_STORAGE_DRIVER` and updating the relevant environment variables in your deployment configuration.
If you change the storage driver (for example, from `local` to `s3` or vice versa), **existing artifacts will not be automatically migrated**.
63
+
To regenerate artifacts:
48
64
49
-
More details can be found in the [configuration documentation](../reference/configuration).
65
+
- You must either delete the old artifacts, or
66
+
- Manually update their checksum values and regenerate them.
67
+
68
+
Failing to do so may result in missing or stale artifact files.
69
+
:::
70
+
71
+
---
50
72
51
73
## Object model
52
74
53
-
Objects or files stored within the object-storage, are identified by an identifier (UUID). An identifier is assigned to the object at time of creation within the object-storage. Interactions with the object then happen leveraging that identifier.
75
+
Objects or files stored within object storage are identified by a unique identifier (UUID). This identifier is assigned when the object is created. All interactions with the object use this identifier.
76
+
77
+
For more details on configuration options, see the [Infrahub configuration reference](../reference/configuration.mdx).
0 commit comments