[ISSUE] include_inherited was silently removed from entity_tag_assignments.list

Open
#1,578 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api

Research direction

Start with the entity_tag_assignments.list entry point and compare its include_inherited behavior in SDK versions 0.133.0 and 0.134.0. Determine whether the removal is intentional, then verify that the SDK behavior and changelog accurately reflect that decision.

Written by the indexing model from the issue text.

Description

Description
include_inherited was removed from entity_tag_assignments.list in 0.134.0. There is no changelog entry for this change.

e.g.

from databricks.sdk import WorkspaceClient
client = WorkspaceClient()
client.entity_tag_assignments.list(entity_name=name, entity_type='tables', include_inherited=True)

It appears this was a removal from the API as the docs reflect that, but again i find no mention of the change.

Was this an intentional removal? Why? It seems wrong and gives a chance for error that every user should be responsible for resolving tag inheritance when it appears to be a primary feature via the UI.

Is it a regression?
Works in 0.133.0, remove in 0.134.0 and following versions

Dominant language
Python
Stars
568
Forks
217
Avg merge
1h 1m
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/databricks-sdk-py

All issues in databricks/databricks-sdk-py

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.