* Use federated auth and TME for smoke testsing
- Move to using federated auth
- Move to using TME sub
- Remove other clouds as the public should be enough for smoke testing
* Set default cloud
* Remove testApplicationSecret and run tests under AzPS
* Remove unsupported python 2.7
* Smoke test isolation per package
* Smoke test isolation - remove unnecessary params
* Passing in single artifact for smoke test
* Passing in single artifact for smoke test
* Temporarily adding azure-template in requirements-release
* Smoke test isolation per package
* Smoke test isolation - remove unnecessary params
* Passing in single artifact for smoke test
* Passing in single artifact for smoke test
* Temporarily adding azure-template in requirements-release
* Smoke test isolation - ArtifactName fix
* Smoke test isolation - trimming down env matrix
* Smoke test isolation - differentiating nightly build with other builds
* Smoke test isolation per package
* Smoke test isolation - remove unnecessary params
* Passing in single artifact for smoke test
* Passing in single artifact for smoke test
* Temporarily adding azure-template in requirements-release
* Smoke test isolation - ArtifactName fix
* Smoke test isolation - trimming down env matrix
* Smoke test isolation - differentiating nightly build with other builds
* Smoke test isolation
* Smoke test isolation
* Adding displayName for smoke test
* Update eng/pipelines/templates/stages/archetype-python-release.yml
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
* Resolve PR suggestions
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
* smoke test uses new workflow for installing dev feed packages and resolving dependencies
* smoke test dependencies packaging and pkginfo are not required
* add pip freeze to show installed packages
* first cut at grouping dependencies
* describe how dependency version specifiers are combined
* remove requirements.txt work from install_dev_build_dependency.py
* better task name, output requirements_dependencies.txt
* add support for dynamic resource allocation and sovereign cloud testing
* enable normal matrix, add China Cloud
* collapse key_vault_base_async into a type of key_vault_base
* Update common/smoketest/key_vault_base.py --Co-Authored-By: Charles Lowell <chlowe@microsoft.com>
* Update common/smoketest/key_vault_base.py -- Co-Authored-By: Charles Lowell <chlowe@microsoft.com>
* rename AZURE_AUTHORITY_HOST_ALIAS -> AZURE_CLOUD
* import os, DRY up environment variable fetching
* os is required in the key_vault tests because we read the vault URL from it, also add in self to refer to host_alias_map
* rename authorityHostAlias -> azureCloud and set appropriate environment variable in the ARM template
Co-authored-by: Charles Lowell <chlowe@microsoft.com>
* fix async tests and install async requirements
* fix Identity for KV to support AZURE_AUTHORITY_HOST with a hostname (requires hostname without protocol wrapping)
* add AZURE_AUTHORITY_HOST to tests.yml (this one uses a python-specific value because python uses just the host and doesn't use the URL like other languages)
* update naming for authority host variable
* add ability to use gov cloud
* public -> gov for gov cloud instances, tweaks to async event hubs
* update smoke tests to latest version
* smoke test storage version 12.0.0 -> 12.1.0
* string formatting that works in python 2.7 along with a couple other potential fixes for a 2.7 KV certs hang on my laptop
* smoke tests: put executing code into a function and call the funciton instead of importing it directly
* install dependencies from dev pipeline
* what version of pip are we running?
* support both pip 19 and 20 when importing pip internals
* fix eventhubs occasional flakyness
* use the track 2 cosmos preview package
add remaining KV smoke tests back in
add to requirements
allow for other versions of python 3.7
update to use older interfaces
fix up smoke tests for september 2019 preview
name the matrix entry properly
do not wait for cert creation in b3