This repository has been archived by the owner on Feb 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 40
When deploying the service name of the service bus needs to be unique #88
Comments
mgreisen
added a commit
to mgreisen/rest-api-fuzz-testing
that referenced
this issue
Dec 14, 2020
mgreisen
pushed a commit
to mgreisen/rest-api-fuzz-testing
that referenced
this issue
Dec 15, 2020
mgreisen
pushed a commit
to mgreisen/rest-api-fuzz-testing
that referenced
this issue
Dec 15, 2020
mgreisen
pushed a commit
to mgreisen/rest-api-fuzz-testing
that referenced
this issue
Dec 15, 2020
mgreisen
added a commit
that referenced
this issue
Dec 15, 2020
Issue was fixed in PR #88 |
stishkin
added a commit
that referenced
this issue
Jan 6, 2021
* Support for listening on multiple ports in test targets (#58) Co-authored-by: stas <statis@microsoft.com> * Support for a list of swagger specifications (#62) Co-authored-by: stas <statis@microsoft.com> * SwaggerLocations renamed to ApiSpecifications and unify URL and FilePath (#90) Co-authored-by: stas <statis@microsoft.com> * Use "shell" only to run commands (#92) Co-authored-by: stas <statis@microsoft.com> * Make resource names unique #88 (#95) Co-authored-by: Stas <stishkin@live.com> * Refactor schema to include TestTargetConfiguration as common configuration for test tasks (#94) - TestTargetConfiguration includes ApiSepcifications list, IP, port and host (all are optional) - If task sets it's own TestTargetConfiguration, then it overrides the global one Co-authored-by: stas <statis@microsoft.com> * Expose more of RESTler configuration settings as part of Run Configuration (#98) Co-authored-by: stas <statis@microsoft.com> * Schema renames (#99) * Rename: testTargetConfiguration -> targetConfiguration * Rename: targets -> services * Script to run all samples Co-authored-by: stas <statis@microsoft.com> * "dredd" integration with RAFT (#101) Co-authored-by: stas <statis@microsoft.com> * use endpoint for target under test configuration (#102) Co-authored-by: stas <statis@microsoft.com> * - dedicated results storage (#103) - all of utils functionality (status tables, azure function blob storage) move to utils storage Co-authored-by: stas <statis@microsoft.com> * Refactor RAFT specific code into separate libraries, thus simplifying onboarding of tools written in node-js or Python (#104) Co-authored-by: stas <statis@microsoft.com> * Align docs with V2 changes (#105) Co-authored-by: stas <statis@microsoft.com> Co-authored-by: stas <statis@microsoft.com> Co-authored-by: Marc <marc@greisen.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently if we have a deployment named "demo" we will create a service bus named "demo-raft-servicebus" this name must be unique across azure. If a demo service has been created somewhere else deployment will fail.
We should add the same uniqueness we've added elsewhere using the digits from the subscription as part of the name.
The text was updated successfully, but these errors were encountered: