Skip to content

Add Deploy to Container App with Copilot command #965

Merged
motm32 merged 13 commits intomainfrom
meganmott/deployWithCopilot
Nov 19, 2025
Merged

Add Deploy to Container App with Copilot command #965
motm32 merged 13 commits intomainfrom
meganmott/deployWithCopilot

Conversation

@motm32
Copy link
Copy Markdown
Contributor

@motm32 motm32 commented Aug 27, 2025

This add a new command using CopilotUserInput so copilot will provide all suggestions for the prompt steps.

Here is a video of how the new process looks (some of the wording in the video has been changed):

DeployToContainerAppWitCopilot.mp4

Essentially what happens is once the command starts running a loading web view panel screen will pop up. Then once the copilot responses have generated the summary view will pop up where users can either confirm or make edits.

Todo:

  • Update the utils package once released
  • If copilot gives an invalid response and it is popped back to the user discard of the loading view

Copy link
Copy Markdown
Member

@nturinski nturinski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me.

Just thinking out loud, but I think in the future, all the wrapper code you put into deployContainerApp may be better to make a util function that basically just wraps the command with all of the Copilot trappings. It should make it easier to just apply to all of our commands.

const confirmationViewDescription: string = localize('viewDescription', 'Please select an input you would like to change. Note: Any input proceeding the changed input may need to change as well');
const confirmationViewTabTitle: string = localize('deployContainerAppTabTitle', 'Summary - Deploy Image to Container App');
const title: string = localize('deployContainerAppTitle', 'Deploy image to container app');
let confirmationViewDescription: string = localize('viewDescription', 'Please select an input you would like to change. Note: Any input proceeding the changed input may need to change as well');
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Right now, it's not a may, it's guaranteed that it needs to change, right?

Also maybe we should note that a changed input may lead to different prompts?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure how granular it needs to be? I will change it from may to need but I think the different prompts may be adding more info than necessary and will make the description longer. If you are that passionate about it though I can make that change 😅

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should know that I'm not passionate about anything lol. It's also prefixed with a nit 😋

@MicroFish91
Copy link
Copy Markdown
Contributor

MicroFish91 commented Oct 30, 2025

Very cool. I bet prompt by prompt progress updates in the future could really elevate that loading page too

Oh and let's hold off and merging this until the next release cycle. I'm about to send off the current build for test

@MicroFish91
Copy link
Copy Markdown
Contributor

Okay we released, so should be okay to start merging new changes!

@motm32 motm32 merged commit b8ac537 into main Nov 19, 2025
2 checks passed
@motm32 motm32 deleted the meganmott/deployWithCopilot branch November 19, 2025 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants