Azure feed with BaseURI fails
See original GitHub issueSteps
- Create a new azure feed
- Set
baseURI
in sleet.json - Init
E:\tmp> .\Sleet.exe init --verbose
[System.InvalidOperationException] Unable to make 'https://example.com/test/sleet.settings.json' relative to 'https://sleettestfeed.blob.core.windows.net/basetest/'
This works for local feeds, but not for azure feeds.
//cc @natemcmaster
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Azure Artifacts Private npm Feed Authentication Failed
A few months ago I created a private npm feed in Azure Artifacts. Authentication with this feed worked fine.
Read more >NULL being passed from pipeline to linked service baseURL
I have parameterized the linked service baseURL and this works when testing from the linked service, and from the dataset. When I try...
Read more >Feed GUID not recognized for project-scoped feeds #40
This happens in a hosted Ubuntu agent with a project-scoped feed with default permissions. It's exactly the same error (feed not found) ...
Read more >Configure permissions - Azure Artifacts
How to configure permissions for Artifacts feeds, views, and pipelines access.
Read more >Azure OpenAI Service REST API reference
The status field can be "notRunning" (task is queued but hasn't started yet), "running" , "succeeded" , "canceled" (task has timed out), "failed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Not really a user error! 😄 The config settings are confusing right now, I’ll keep this open to track documenting them and improving the error messages.
I’ve done some clean up around how baseURI is handled. This is fixed now and I’ve added an azure test to verify it.