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.

Sign up for GitHub

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

Jump to bottom

[Search] Reenable and rerecord tests that require storage account access #48588

Open
kinelski opened this issue Mar 6, 2025 · 0 comments
Open

[Search] Reenable and rerecord tests that require storage account access #48588

kinelski opened this issue Mar 6, 2025 · 0 comments
Assignees
@kinelski
Labels
Client This issue points to a problem in the data-plane of the library. Search

Comments

@kinelski
Copy link
Member

kinelski commented Mar 6, 2025

The following tests have been disabled in playback mode since they require storage account access to be rerecorded:

  • CreateAzureBlobIndexer
  • CrudDataSourceConnection
  • CrudSkillset
  • RoundtripAllSkills
  • CreateIndexerAsync (sample)

These are expected to work if rerecorded using our TME subscription. Another option we could explore would be updating the tests to use identity-based authentication instead.
@kinelski kinelski self-assigned this Mar 6, 2025
@kinelski kinelski added Search Client This issue points to a problem in the data-plane of the library. labels Mar 6, 2025
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 6, 2025
@kinelski kinelski mentioned this issue Mar 6, 2025
Merged
@jsquire jsquire removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kinelski kinelski

Labels
Client This issue points to a problem in the data-plane of the library. Search
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jsquire @kinelski