Skip to content

Comments

Publish DataAsset Apis#40471

Open
AnilKumarPolepalli wants to merge 10 commits intoAzure:mainfrom
AnilKumarPolepalli:PublishDataassetAPIs
Open

Publish DataAsset Apis#40471
AnilKumarPolepalli wants to merge 10 commits intoAzure:mainfrom
AnilKumarPolepalli:PublishDataassetAPIs

Conversation

@AnilKumarPolepalli
Copy link
Member

@AnilKumarPolepalli AnilKumarPolepalli commented Feb 16, 2026

Choose a PR Template

Publishing DataAsset APIs. These are previously(old) developed APIs that were not pushed in the last release.

DataAssets_Create
DataAssets_CreateRelationship
DataAssets_DeleteById
DataAssets_DeleteRelationship
DataAssets_GetById
DataAssets_List
DataAssets_ListRelationships
DataAssets_Query
DataAssets_Update

@github-actions
Copy link

github-actions bot commented Feb 16, 2026 •
edited
Loading

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ This PR has at least one change violating Azure versioning policy (label: VersioningReviewRequired).
    To unblock this PR, either a) introduce a new API version with these changes instead of modifying an existing API version, or b) follow the process at aka.ms/brch.
  • ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.


Comment generated by summarize-checks workflow run.

@github-actions github-actions bot added data-plane TypeSpec Authored with TypeSpec labels Feb 16, 2026
@github-actions
Copy link

github-actions bot commented Feb 16, 2026 •
edited
Loading

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Azure.Analytics.Purview.UnifiedCatalog
TypeSpec PurviewUnifiedCatalog

@github-actions github-actions bot added the VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required label Feb 16, 2026
@AnilKumarPolepalli AnilKumarPolepalli added linter-issues BreakingChange-LintDiff suppressions for LintDiff errors labels Feb 16, 2026
Anil Kumar Polepalli (Quadrant Technologies LLC) added 7 commits February 16, 2026 16:16
Fix missing newline at end of file in multiple JSON and TSP files
2ac7f47
Refactor Data Asset Model and Examples
f902f46 
- Updated Data Asset names from "myDataProduct" to "myDataAsset" for consistency.
- Enhanced system data model to include provisioning state and expiration details.
- Modified contact structure to support multiple roles (owner, expert, databaseAdmin).
- Changed server endpoint URLs to use HTTPS for security.
- Updated example JSON files to reflect new model changes and ensure accurate API responses.
- Renamed dataMapAssetIds to sourceAssetIds in query requests for clarity.
- Improved documentation for various models and properties to enhance understanding.
Add ContactsMap model and update contacts references in data models a…
d925937 
…nd API service
Update contact structure in JSON examples and models for consistency
cc2f11e
Refactor data asset provisioning state to use 'provisionedValue' inst…
31c34d5 
…ead of 'provisioningState' across multiple JSON examples and models. Removed lineage information from various examples and updated related API specifications to reflect these changes.
Refactor lineage property in DataAsset model to use LineageObject for…
d565654 
… improved structure and clarity in API specifications.
Update provisioning state in DataAsset examples and models to use 'pr…
8d121f6 
…ovisioningState' instead of 'provisionedValue'; add includeExtendedProperties and includeLineage parameters to GetById example.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

BreakingChange-LintDiff suppressions for LintDiff errors data-plane linter-issues TypeSpec Authored with TypeSpec VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@AnilKumarPolepalli