Skip to content

Commit 5582d58

Browse files
aravind-seguaravind-segu
committed
Undo file deletions
1 parent 41f197b commit 5582d58

File tree

3 files changed

+157
-0
lines changed

3 files changed

+157
-0
lines changed

‎docs/account/settings/disable_legacy_features.rst‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
``a.settings.disable_legacy_features``: Disable Legacy Features
2+
===============================================================
3+
.. currentmodule:: databricks.sdk.service.settings
4+
5+
.. py:class:: DisableLegacyFeaturesAPI
6+
7+
Disable legacy features for new Databricks workspaces.
8+
9+
For newly created workspaces: 1. Disables the use of DBFS root and mounts. 2. Hive Metastore will not be
10+
provisioned. 3. Disables the use of ‘No-isolation clusters’. 4. Disables Databricks Runtime versions
11+
prior to 13.3LTS.
12+
13+
.. py:method:: delete( [, etag: Optional[str]]) -> DeleteDisableLegacyFeaturesResponse
14+
15+
Delete the disable legacy features setting.
16+
17+
Deletes the disable legacy features setting.
18+
19+
:param etag: str (optional)
20+
etag used for versioning. The response is at least as fresh as the eTag provided. This is used for
21+
optimistic concurrency control as a way to help prevent simultaneous writes of a setting overwriting
22+
each other. It is strongly suggested that systems make use of the etag in the read -> delete pattern
23+
to perform setting deletions in order to avoid race conditions. That is, get an etag from a GET
24+
request, and pass it with the DELETE request to identify the rule set version you are deleting.
25+
26+
:returns: :class:`DeleteDisableLegacyFeaturesResponse`
27+
28+
29+
.. py:method:: get( [, etag: Optional[str]]) -> DisableLegacyFeatures
30+
31+
Get the disable legacy features setting.
32+
33+
Gets the value of the disable legacy features setting.
34+
35+
:param etag: str (optional)
36+
etag used for versioning. The response is at least as fresh as the eTag provided. This is used for
37+
optimistic concurrency control as a way to help prevent simultaneous writes of a setting overwriting
38+
each other. It is strongly suggested that systems make use of the etag in the read -> delete pattern
39+
to perform setting deletions in order to avoid race conditions. That is, get an etag from a GET
40+
request, and pass it with the DELETE request to identify the rule set version you are deleting.
41+
42+
:returns: :class:`DisableLegacyFeatures`
43+
44+
45+
.. py:method:: update(allow_missing: bool, setting: DisableLegacyFeatures, field_mask: str) -> DisableLegacyFeatures
46+
47+
Update the disable legacy features setting.
48+
49+
Updates the value of the disable legacy features setting.
50+
51+
:param allow_missing: bool
52+
This should always be set to true for Settings API. Added for AIP compliance.
53+
:param setting: :class:`DisableLegacyFeatures`
54+
:param field_mask: str
55+
Field mask is required to be passed into the PATCH request. Field mask specifies which fields of the
56+
setting payload will be updated. The field mask needs to be supplied as single string. To specify
57+
multiple fields in the field mask, use comma as the separator (no space).
58+
59+
:returns: :class:`DisableLegacyFeatures`
60+

‎docs/workspace/catalog/temporary_table_credentials.rst‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
``w.temporary_table_credentials``: Temporary Table Credentials
2+
==============================================================
3+
.. currentmodule:: databricks.sdk.service.catalog
4+
5+
.. py:class:: TemporaryTableCredentialsAPI
6+
7+
Temporary Table Credentials refer to short-lived, downscoped credentials used to access cloud storage
8+
locationswhere table data is stored in Databricks. These credentials are employed to provide secure and
9+
time-limitedaccess to data in cloud environments such as AWS, Azure, and Google Cloud. Each cloud provider
10+
has its own typeof credentials: AWS uses temporary session tokens via AWS Security Token Service (STS),
11+
Azure utilizesShared Access Signatures (SAS) for its data storage services, and Google Cloud supports
12+
temporary credentialsthrough OAuth 2.0.Temporary table credentials ensure that data access is limited in
13+
scope and duration, reducing the risk ofunauthorized access or misuse. To use the temporary table
14+
credentials API, a metastore admin needs to enable the external_access_enabled flag (off by default) at
15+
the metastore level, and user needs to be granted the EXTERNAL USE SCHEMA permission at the schema level
16+
by catalog admin. Note that EXTERNAL USE SCHEMA is a schema level permission that can only be granted by
17+
catalog admin explicitly and is not included in schema ownership or ALL PRIVILEGES on the schema for
18+
security reason.
19+
20+
.. py:method:: generate_temporary_table_credentials( [, operation: Optional[TableOperation], table_id: Optional[str]]) -> GenerateTemporaryTableCredentialResponse
21+
22+
Generate a temporary table credential.
23+
24+
Get a short-lived credential for directly accessing the table data on cloud storage. The metastore
25+
must have external_access_enabled flag set to true (default false). The caller must have
26+
EXTERNAL_USE_SCHEMA privilege on the parent schema and this privilege can only be granted by catalog
27+
owners.
28+
29+
:param operation: :class:`TableOperation` (optional)
30+
The operation performed against the table data, either READ or READ_WRITE. If READ_WRITE is
31+
specified, the credentials returned will have write permissions, otherwise, it will be read only.
32+
:param table_id: str (optional)
33+
UUID of the table to read or write.
34+
35+
:returns: :class:`GenerateTemporaryTableCredentialResponse`
36+

‎docs/workspace/settings/disable_legacy_access.rst‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
``w.settings.disable_legacy_access``: Disable Legacy Access
2+
===========================================================
3+
.. currentmodule:: databricks.sdk.service.settings
4+
5+
.. py:class:: DisableLegacyAccessAPI
6+
7+
'Disabling legacy access' has the following impacts:
8+
9+
1. Disables direct access to the Hive Metastore. However, you can still access Hive Metastore through HMS
10+
Federation. 2. Disables Fallback Mode (docs link) on any External Location access from the workspace. 3.
11+
Alters DBFS path access to use External Location permissions in place of legacy credentials. 4. Enforces
12+
Unity Catalog access on all path based access.
13+
14+
.. py:method:: delete( [, etag: Optional[str]]) -> DeleteDisableLegacyAccessResponse
15+
16+
Delete Legacy Access Disablement Status.
17+
18+
Deletes legacy access disablement status.
19+
20+
:param etag: str (optional)
21+
etag used for versioning. The response is at least as fresh as the eTag provided. This is used for
22+
optimistic concurrency control as a way to help prevent simultaneous writes of a setting overwriting
23+
each other. It is strongly suggested that systems make use of the etag in the read -> delete pattern
24+
to perform setting deletions in order to avoid race conditions. That is, get an etag from a GET
25+
request, and pass it with the DELETE request to identify the rule set version you are deleting.
26+
27+
:returns: :class:`DeleteDisableLegacyAccessResponse`
28+
29+
30+
.. py:method:: get( [, etag: Optional[str]]) -> DisableLegacyAccess
31+
32+
Retrieve Legacy Access Disablement Status.
33+
34+
Retrieves legacy access disablement Status.
35+
36+
:param etag: str (optional)
37+
etag used for versioning. The response is at least as fresh as the eTag provided. This is used for
38+
optimistic concurrency control as a way to help prevent simultaneous writes of a setting overwriting
39+
each other. It is strongly suggested that systems make use of the etag in the read -> delete pattern
40+
to perform setting deletions in order to avoid race conditions. That is, get an etag from a GET
41+
request, and pass it with the DELETE request to identify the rule set version you are deleting.
42+
43+
:returns: :class:`DisableLegacyAccess`
44+
45+
46+
.. py:method:: update(allow_missing: bool, setting: DisableLegacyAccess, field_mask: str) -> DisableLegacyAccess
47+
48+
Update Legacy Access Disablement Status.
49+
50+
Updates legacy access disablement status.
51+
52+
:param allow_missing: bool
53+
This should always be set to true for Settings API. Added for AIP compliance.
54+
:param setting: :class:`DisableLegacyAccess`
55+
:param field_mask: str
56+
Field mask is required to be passed into the PATCH request. Field mask specifies which fields of the
57+
setting payload will be updated. The field mask needs to be supplied as single string. To specify
58+
multiple fields in the field mask, use comma as the separator (no space).
59+
60+
:returns: :class:`DisableLegacyAccess`
61+

0 commit comments

Comments
 (0)