Azure / Azure/azure-rest-api-specs
[ARM AppConfiguration] Hardcoded subscription id breaks Smoke Tests
Open
App Configuration
ARM
Service Attention
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
There are a few hardcoded subscription Ids in the examples for AppConfiguration. This is breaking JS smoke tests.
The examples shouldn't hardcode subscription Ids. Maybe we should have a lint rule for this.
/cc: @mikeharder, @weshaggard , @maorleger
Contributor guide
Research direction
Search the AppConfiguration examples for hardcoded subscription IDs and inspect the JavaScript smoke tests that currently fail. Replace the example-specific values with a non-hardcoded approach, then run the affected smoke tests and verify that no subscription IDs remain hardcoded; the possible lint rule is not defined further in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cloud, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100