Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Custom URL and Key #93

Open
denelon opened this issue Nov 3, 2021 · 0 comments
Open

Custom URL and Key #93

denelon opened this issue Nov 3, 2021 · 0 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Milestone
v.Next-REST

Comments

@denelon
Copy link
Contributor

denelon commented Nov 3, 2021

Description of the new feature / enhancement

We want to be able to support a REST source being hosted on infrastructure other than just Azure.

This would not impact the reference implementation, but additional improvements need to be made to have the PowerShell cmdlets communicate with any REST implementation. Note: the New-WinGetSource will continue to support only Azure, but the other cmdlets will be using the "management" REST endpoints and not connecting with Azure resources directly.

Proposed technical implementation details

No response
@denelon denelon added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 3, 2021
@denelon denelon added this to the v.Next-REST milestone Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Projects
None yet
Milestone
v.Next-REST
Development

No branches or pull requests
1 participant
@denelon