- Making some changes to simplify the "duplicate" models that we're exporting to mirror the opentelemetry models (addresses feedback from @xirzec and @bterlson)
- Switch core-tracing back to the `-preview` version naming style. Changing it mid-stream like we did breaks internal tooling.
* Update live test templates to use matrix generation
* Update sdk live tests to use matrix generation, cloud config stages
* Fix live test matrix filter parity errors
* Remove matrix filters. Opt-in most tests to samples and min/max testing
* Fix post step template parameter in monitor live tests
* Filter dependency version for live tests that don't support it
* Only publish test results for browser and node tests
* [template] Make README Logging section consistent
We might have introduced the inconsistency for some libraries while copying
content from other languages.
* Update other README files
Contents for messaging libraries (Event Hub/Service Bus) remain unchanges
because they are different in having additional information about `rhea`
logging.
* linking to logger
As part of prepping for the next release of OpenTelemetry we found some code patterns that were going to become a large maintenance burden for us, primarily around the parenting of spans. To make this easier I've removed as many duplicate implementation of createSpan and tried to centralize everything into core-tracing instead.
This won't completely remove changes needed for a newer version of OpenTelemetry but it'll eliminate one of the bigger bottlenecks.
* [EventGrid] Update core-auth reference
In b6040c5451 we took a dependency on
some new surface area in @azure/core-auth. That has now been released as
version 1.2.0, so we bump our minimum dependency to that version.
The other packages have been updated as well, to keep versions consistent.
* [EventGrid] Prepare for 3.0.0-beta.3 release
This PR removes our dependency on the unmaintained package "karma-remap-istanbul" and replaces it with a smaller karma plugin ("karma-sourcemap-loader") that allows karma-coverage to load source maps from the disk correctly.
I tested and confirmed that the generated coverage data has the correct source TS files.
* [Docs] Upgrade typedoc to v0.15.2 to match that used by docs team
* standardize the docs script for cosmos, kv-admin, comm-common, and storage-internal-avro
This newly added command `docs` can help increase the quality of our documentation comments. It enables us to have a tight feedback loop on what is being generated as a documentation of our packages. I am pinning `typedoc` to v0.15.0 for now because this is the version being used for generating docs at `docs.microsoft.com`. This version should be updated when that team updates theirs.
Fixes https://github.com/Azure/azure-sdk-for-js/issues/12928
* upgrade TS version and fix compilation issues
* upgrade the linting parser version and fix new linting issues
* fix cosmos sample
* address feedback
* fix linting issues in formrecognizer tests
* use unknown instead of any across our code
* address more issues
* cleanup package.json in core-http
* revert noisy linting changes caused by vanilla eslint rules not TS aware
* allow the poller to have results of type void
* fixing samples
* fix keyvault-certificates' sample
* Open up Buffered Sender Configurations
* Response to PR Comments
* Update API File
* Added Jitter value
* PR Comments II
* Add jitterValue to the correct place
* Format
* Sync Retry Logic with core-https
* Changed Name to initialBatchActionCount
* Update API
* Regenerated Search SDK Data MD
* Custom Code changes for previous auto generated Data MD changes
* Regenerated Search SDK Service MD
* Custom Code changes for previous auto generated Service MD changes
* Added Test Cases for Search Index Client
* New Recordings
* Additional Changes
* Another set of recordings
* Some more changes
* Refactorings based on PR Comments
* Formatting Changes
* update the CONTRIBUTING.md guide to point to the automatic debug configuration feature in vscode
* delete all custome vscode configs
* factoring out coverage scripts so that mocha with ts-node can work with vscode debugger
* Added Test cases for Search Client
* Added recordings
* Test with Harmony Flag
* Update sdk/search/search-documents/test/node/searchIndexClient.spec.ts
Co-authored-by: Jeff Fisher <xirzec@xirzec.com>
* Code changes for PR comments
Co-authored-by: Jeff Fisher <xirzec@xirzec.com>
* add ability to skip smoke tests based on the presence of environment variables
parameterize test-resources.json
disable cosmos db smoke testing in china cloud
add --ci to smoke test execution
add yargs to smoke tests
smoke tests: @types/yargs is unnecessary, add await in app
turns out @types/yargs is required
use KeyVaultSecrets instead of this
incremental sample compiling progress
first cut at using sample format for smoke tests
Smoke test deploys, onboards samples
Fix pre-samples.js
Add environment variable output to New-TestResources.ps1
Update smoke test package.json
Update-SmokeTests.ps1 - variable outputs for CI, start documenting
New-TestResources.ps1 output environment variables
Update smoke tests yaml
* Remove Smoke Test resources in yaml
* parameters
* Update smoke-tests.yml
* Fix prep-samples.js
* Remove extra *
* Formatting for prep-samples.js
* Revert "Remove extra *"
This reverts commit f0c1b3f36b474f09d2cd49ee2abb327ad0236f10.
* Move Node version higher so Update-SmokeTests.ps1 can use it
* node run.js
* Set AZURE_RESOURCEGROUP_NAME at the top level so delete scripts can clean up after
* Add run.js
* Give ability to specify blank service directory in remove-test-resources.yml
* Add ability to specify resource group name directly to New-TestResources.ps1
* Add devops logging for smoke test failures
* Better command layout
* Update KV test resources to include KEYVAULT_URI for samples
* Fix App Config and KV to use environment variables from the test-resources.json
* Add in package.json configuration to skip certain failing files in smoke tests
* Add ability to skip samples based on configuration information in package.json
* Remove ArmTemplateParameters from smoke tests
* Delete test resources after 24 hours
* Add contacts.js (timing out) to skip
* Add deleteAndRecover.js to skip list
* Skip backupAndRestore.js in KV Secrets
* Improve smoke test error logging
* Skip useProxy.js in Service Bus smoke tests
* Use ARM template params in sovereign clouds
* Remove base smoke test cases
* Use configruable storage endpoint suffix in event hub ARM template
* Use baseName for the basis of the GUID
* Set environment variables from standard config
* Set sample directory when running each test to preserve sample context
* Idempotent naming
* Force $CI to $false
* Use proces.cwd() instead of __dirname
* Skip samples where confiugrations are not present in test-resources.json
* Add support for storage endpoint suffix to storage test-resources.json
* Also exclude copyModel.js
* Compute account name for text analytics so we don't collied with test resources that have the same name
* Add endpoint information for cognitive services
* Skip some storage tests because of hardcoded endpoint suffix
* Skip ai-text-analytics pending further investigation
* Proper spelling for customPipeline
* New-TestResources -- if $CI is true AND a ResourceGroupName is specified, do not mututae the $BaseName
* Always generate a new $BaseName when $CI is $true. If we don't do this and reuse $BaseName then multiple resources of the same type might get deployed with the same name and there will be collisions
* Remove samples-manifest.json
* Use static name for cognitive services user role assignment to avoid smoke test collision
* Form Recognizer should use resource group location
* Role assignment names must be GUIDs
* Update search SKU so deployment succeeds
* Fix form recognizer and text analytrics ARM templates to assign RBAC roles directly to the resources
* Unique guid for Text Analytrics role assignment
* Use relative paths in Initialize-SmokeTests.ps1
* Add --use-packages to samples prep to use package references instead of source references
* Move //smokeTestConfiguration from samples package.json to the package's package.json
* Add in better path support
* Update Smoke Test README.md
* Use globbing to find samples/javascript folders inside packages
* Remove extra files
* Remove hard coded test cases
* Remove smoke-test/test-resources.json
* Use context to set AZURE_AUTHORITY_HOST
* Spacing
* Document -ResourceGroupName parameter
* workingDirector -> workingDirectory
* no inputs
* Skip template samples as the samples do not run properly
* Set environment variables for test application in the initilize script
* Exclude authenticationMethods.js and recognizeContent.js samples because of smoke test errors
* Remove setting AZURE_AUTHORITY_HOST in New-TestResources.ps1 and set it in Initialize-SmokeTest.ps1
* Review feedback: use APPCONFIG_CONNECTION_STRING in samples and tests
* Review feedback KEYVAULT_NAME -> KEYVAULT_URI in all samples and docs for KV
* Make sample.env files consistent
* Skip deploying and onboarding when there is no test-resources.json file
* Standardize prettier configurations across the repo
* update relative paths
* rushx format text analytics
* ignore api.md files
* adding ignore-path parameter to the check-format and format scripts in keyvault-admin
* Azure SDK dev-tool first pass
* [dev-tool] dev-tool dev-samples and fixes to all commands
* Nested command structure
* Better argument parsing, type-checking, and recursive command structure. Added support for running a single sample.
* Added dev-tool README
* [ai-text-analytics] Update package.json to use new script.
* Removed some development cruft
* prettier + eslint
* Quick fix to ParsedOptions type
* WIP
* Command framework improvements
* Basic unit-tests for package resolution.
* One more test, assorted changes
* README update
* Migrated all packages with sample code to use dev-tool
* Added dummy integration-test stub
* Added dummy integration-test stub for eslint plugin
* Added dummy integration-test:browser stubs
* Added dev-tool dependency to packages using it
* Corrected build:samples step in package.json
* WIP
* [dev-tool] ts-to-js command
* [dev-tool] leaf command test
* Fixed more deeply nested samples due to shared code
We use an async function to add a recorded request to an array then
save the array to files when recorder stops. However we did not wait
for the async function to complete, which leads to recording missing
requests. This issue only happens in the browser case. In Node it is
done in synchronous way.
This change makes recorder to wait until all the recorded
requests are added before saving them.
All the tests have been updated to await for `recorder.stop()`.
Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
* Bump dependency core-http version to 1.1.4
to ensure that all packages have the `x-ms-useragent` browser header key change
for telemetry.
* Make exception for storage
* Add sentinel value to connection string
* Update sdk/search/search-documents/src/searchIndexerClient.ts
Co-authored-by: Jeff Fisher <xirzec@xirzec.com>
Co-authored-by: Jeff Fisher <xirzec@xirzec.com>
* Add initial Refs for repositiory
* Initial Changes to refs JS
* Switch template referencing to use extends
* Remove resources from archetype-sdk-integration.yml
* Refactor SearchServiceClient into SearchIndexClient and SearchIndexerClient
* Handle selected properties for List operations
* Add delete methods by model
* Response to PR Comments
* Minor Typo
* Dummy Commit I
* Dummy Commit II
* Include sourcemap file in karma files section
so we can debug TypeScript source code for browser tests. One still
needs to disable code coverage first though to have the source mapping
working.
We Have to set the .js.map files' type to be 'html' to prevent karma from
treating them as the default js files. See http://karma-runner.github.io/5.0/config/files.html for more details.
* one matrix to live test them all
* clean up environment vars and test configurations
* working template logic for browser and sample testing
* disable samples testing for form recognizer until it's ready for nightly live runs
* use Node 10 for samples
* Readme content of Azure Search Documents is unclear
* Minor change
* Adding some more information
* Updated based on PR Comments
* Minor change
* Minor spell change
* Update sdk/search/search-documents/README.md
Co-authored-by: Jeff Fisher <xirzec@xirzec.com>
* nit
Co-authored-by: Jeff Fisher <xirzec@xirzec.com>
This PR is here to save us from the Deploy button rabbit hole and put us back in track with powershell.
The Deploy Button approach has considerable caveats. Some of them being:
The forms they generate don't provide a lot of tooling to explain how to fill these properties.
The forms they generate require considerable knowledge to feel its properties.
They appear to be simple at a first glance, but they require considerable documentation to make them viable for general users.
Instead of continuing to go the route of Deploy Buttons, we can re-use the PowerShell programs that have been made available in out TS/JS SDK just as well as they exist in the other languages' SDKs, and which have already been documented once at the root of the project, and only make reference to these tools in the test folders, where contributors will surely check. Other general consumers should be safe by ignoring these and simply following the available Azure documentation to create any resources for their own programs, without having to worry about the specific needs of our integration tests.
This PR does the same change on all of the other projects that have test-resources.json.
Once this is merged, the following issues will be solved:
Closes#7532 , since it will be OK to keep template parameters in the ARM templates.
Closes#7366 , since the new indications will suffice.
Closes#7365 , since the new indications will suffice.
Closes#7364 , since the new indications will suffice.
Closes#7363 , since the new indications will suffice.
Closes#6647 , since there will be no remaining pending tasks.
Co-authored-by: Ramya Rao <ramya.rao.a@outlook.com>
* Update contributing sections to link to CONTRIBUTING.md
* Update the contributing section for rest of libraries
* Remove old CONTRIBUTING.md files
README should point to the main CONTRIBUTING.md under repository root.
We did similar changes earlier (e.g., 73f7f90c4) however these seem leftover
that got missed.
* Link to storage specific contributing guide
* Add integration test tasks to eslint plugin
* Fix GeographyPoint serialization
* Add test and get it working inside node
Since SearchServiceClient doesn't work in the browser, will have to investigate a way to run SearchIndexClient tests there.
* Code changes for list indexers operation.
* Code changes for create indexer operation
* Code changes for Get Indexer operation
* Code changes for create/update indexer
* Code changes for Delete indexer operation
* Code changes for Get Indexer Status operation
* Code changes for reset index operation
* Code changes for run index operation
* Remove select & change indexer name in Readme file
* Adding fields to List Ops
* PR Comments
* mocha-multi-reporter.js
* update test commands in package.json to not use mocha-multi
* remove mocha-multi from devDependencies
* Update mocha to ^7.1.1
* ts-mocha@6.0 doesn't support mocha@7.0.0 - removing since not being used
ERROR @rush-temp/event-hubs: ts-mocha@6.0.0 requires a peer of mocha@^3.X.X || ^4.X.X || ^5.X.X || ^6.X.X but version
7.1.1 was installed.
* generate pnpm-lock file
* `rush update --full` since mocha-multi has been removed
* rollback mocha to 6.2.2 since some of the tests require updates
* generate pnpm-lock file
* update core-http's reporter
* unit-test:browser and unit-test:node commands for eslint plugin to nullify errors thrown by rush
* update core-arm reporter
* Add copyright header
* Remove console.logs
* pnpm-lock from master
* [core][search] log additional headers on requests
Updates the standard list of logged headers to include CORS headers.
Also, adds service-specific allowed headers to the SearchIndexClient.
Fixes#7644
* resolved conflicts in arm-compute package
* Moved arm-cognitiveservices
* Moved arm-cosmosdb
* Moved arm-hanaonazure
* Moved arm-hdinsight
* Moved arm-iotcentral
* Moved arm-iothub
* Moved arm-iotspaces
* Moved arm-kusto
* Moved arm-labservices
* Moved arm-links
* Moved arm-locks
* Moved arm-logic and arm-machinelearningcompute
* Moved arm-machinelearningexperimentation
* Moved arm-machinelearningservices
* Moved arm-managedapplications
* Moved arm-managementgroups
* Moved arm-managementpartner
* Moved arm-maps
* Moved arm-mariadb
* Moved arm-marketplaceordering
* Moved arm-mediaservices
* Moved arm-migrate
* Moved arm-mixedreality
* Moved arm-monitor
* Moved arm-msi
* Moved arm-mysql
* Moved arm-netapp
* Moved arm-network
* Moved arm-notificationhubs
* Moved arm-operationalinsights
* Moved arm-operations
* Moved arm-policy
* Moved arm-policyinsights
* Moved arm-postgresql
* Moved arm-powerbidedicated
* Moved arm-powerbiembedded
* Moved arm-privatedns
* Moved arm-recoveryservices
* Moved arm-recoveryservices-siterecovery
* Moved arm-recoveryservicesbackup
* Moved arm-rediscache
* Moved arm-relay
* Moved arm-reservations
* Moved arm-resourcegraph
* Moved arm-resourcehealth
* Moved arm-resources
* Moved arm-search
* Moved arm-security
* Moved arm-servicebus
* Moved arm-servicefabricmesh
* Moved arm-servicemap
* Moved arm-signalr
* Moved arm-sql
* Moved arm-sqlvirtualmachine
* Moved arm-storage
* Moved arm-storageimportexport
* Moved arm-storagesync
* Moved arm-storsimple1200series
* Moved arm-storsimple8000series
* Moved arm-streamanalytics
* Moved arm-subscriptions
* Moved arm-timeseriesinsights
* Moved arm-trafficmanager
* Moved arm-visualstudio
* Moved arm-webservices
* Moved arm-workspaces
* moved arm-workspaces and arm-webservices under machinelearning service folder
* Moved arm-commitmentplans
* Moved arm-containerregistry
* Moved arm-containerservice
* fixed the repo structure for arm-containerservice
* updated service folder for arm-operations
* updated service folder for arm-subscriptions
* updated service folder for arm-recoveryservices-siterecovery
* updated service folder for arm-servicemap
* updated service folder for arm-rediscache
* updated service folder for arm-rediscache