-
Notifications
You must be signed in to change notification settings - Fork 17
Add Basic and Advanced flow for Deploy Workspace Project
#961
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.
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
Changes from 41 commits
aaf27f2
149eb14
2b14722
42bc11a
7e0e6b3
9ab8315
9a50407
5bad23c
069eda8
40b315e
570c755
f7de2a0
5a81bb5
c1ef5fc
e13e6ae
66ad27a
b749915
8f3b048
2fc34be
63f8333
f9ef062
09025a0
5275048
63de6ea
4182ccf
b1ebac5
4f67144
c4deb93
efd8a27
f5cc187
4d843b2
993e38d
34b9cc2
48af602
3c36a95
666b13d
6b22fe8
c0a9fee
4f49a71
301512e
d0e61a4
18f3788
e888533
f7fbfd7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,20 +1,21 @@ | ||
| # Change Log | ||
|
|
||
| ### 0.0.3 | ||
| ## 1.0.0 | ||
| ### Changed | ||
| * [[961](https://github.com/microsoft/vscode-azurecontainerapps/pull/961)] Add a new resource location parameter to the `deployWorkspaceProjectApi` definition. If no location is provided, try to infer location via other provided resources. | ||
| * [[961](https://github.com/microsoft/vscode-azurecontainerapps/pull/961)] Suppress registry prompting by default and remove associated flag (`suppressRegistryPrompt`) | ||
|
|
||
| ## 0.0.3 | ||
| ### Added | ||
| * [[817]](https://github.com/microsoft/vscode-azurecontainerapps/pull/817) Added an API entry-point and compat wrapper for existing `deployImageApi` command | ||
|
|
||
| ### Changed | ||
| * [[816]](https://github.com/microsoft/vscode-azurecontainerapps/pull/816) Added backward compatibility to ensure existing functionality remains unaffected by new managed identity features. | ||
|
|
||
| ### 0.0.2 | ||
|
|
||
| ## 0.0.2 | ||
| ### Changed | ||
| * [[615]](https://github.com/microsoft/vscode-azurecontainerapps/pull/615) Removed ability to set option `ignoreExistingDeploySettings`. This will now happen automatically by default. | ||
|
|
||
| ## 0.0.1 | ||
| * Initial release | ||
|
|
||
| ### Added | ||
| * [[578]](https://github.com/microsoft/vscode-azurecontainerapps/pull/578) Added an API entry-point to the `deployWorkspaceProject` command |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,9 +10,7 @@ import type * as api from "./vscode-azurecontainerapps.api"; | |
|
|
||
| export function getAzureContainerAppsApiProvider(): apiUtils.AzureExtensionApiProvider { | ||
| return createApiProvider([<api.AzureContainerAppsExtensionApi>{ | ||
| // Todo: Change this to 0.0.3 later. 0.0.3 is backwards compatible anyway so this change should be fine either way. | ||
| // For some reason it's causing a block on Function side, so just keep it at 0.0.1 until we figure out why | ||
| apiVersion: '0.0.1', | ||
| apiVersion: '1.0.0', | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bump to 1.0.0 because we were running into issues with semver not picking up newer versions when consuming in Functions... something related to needing to start from the first major release version. |
||
| deployImage: deployImageApi, | ||
| deployWorkspaceProject: deployWorkspaceProjectApi, | ||
| }]); | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a few places I've added or switched usage to the new
setAutoSelectLocation. This is because I think it's often times a safer pattern than setting the location directly. This is because setting the location manually doesn't respect when new resource providers are potentially added in the future.