Skip to content
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.

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

feat(ingestion/powerbi): ingest powerbi app #11629

Open
wants to merge 24 commits into
base: master
Choose a base branch
from

Conversation

sid-acryl
Copy link
Collaborator

No description provided.

@sid-acryl sid-acryl changed the title feat(ingestion/powerbi): powerbi app ingestion as dashboard feat(ingestion/powerbi): ingest powerbi app Oct 15, 2024
@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Oct 15, 2024
@aviv-julienjehannet
Copy link
Contributor

Strange error not strictly linked to my PR, I suppose:
https://github.com/datahub-project/datahub/actions/runs/11350486344/job/31568984855?pr=11629#step:12:1720

@sid-acryl
Copy link
Collaborator Author

Strange error not strictly linked to my PR, I suppose: https://github.com/datahub-project/datahub/actions/runs/11350486344/job/31568984855?pr=11629#step:12:1720

It will be fixed now

title="App Ingestion Is Disabled",
message="You are missing workspace app metadata. Please set flag `extract_app` to `true` in recipe to ingest workspace app.",
context=f"workspace-name={workspace.name}, app-name = {workspace.app.name}",
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

do we need a return here? when would .app be populated if app ingestion is disabled?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Added return. .app will be populated on next run after setting extract_app to true

]
)

if edges:
Copy link
Collaborator

Choose a reason for hiding this comment

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

can we make these variable names more clear - edges = dashboards within the app?

also dashboard_urn being the app's urn is super confusing - let's make this more clear

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

app_id: str,
) -> Optional[Dict]:
# [Date: 2024/10/18] As per API doc, the service principal approach is not supported for regular API
# https://learn.microsoft.com/en-us/rest/api/power-bi/apps/get-app
Copy link
Collaborator

Choose a reason for hiding this comment

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

let's add this to the doc on limitations

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It is not going to impact user experience, as we are getting app from AdminApiResolver and I have updated the assets list in doc MD file.

return

# Map to find out which dashboards belongs to the App
dashboard_map: Dict[str, Dict] = {
Copy link
Collaborator

Choose a reason for hiding this comment

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

improve variable naming here

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

@@ -221,6 +229,7 @@ def get_dashboards(self, workspace: Workspace) -> List[Dashboard]:
tiles=[],
users=[],
tags=[],
app_reference=None, # It is getting set later from scan_result
Copy link
Collaborator

Choose a reason for hiding this comment

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

what do we use app_reference for?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed it, not in used

@Daniellundin048
Copy link

respond

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ingestion PR or Issue related to the ingestion of metadata
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants