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.

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

Don't show ingress prompts in draft mode and add additional activity children to core draft commands #814

Merged
merged 41 commits into from
Jan 10, 2025

Conversation

MicroFish91
Copy link
Contributor

@MicroFish91 MicroFish91 commented Dec 24, 2024

Partially addresses part 2 of #719

Examples:

Edit container (edit w/ container registry image):
image

Edit container image (edit w/ workspace project image):
image

@MicroFish91 MicroFish91 marked this pull request as ready for review December 24, 2024 01:54
@MicroFish91 MicroFish91 requested a review from a team as a code owner December 24, 2024 01:54
Copy link
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.

Logically it makes sense to me. My comments are suggestions, but I'm not going to try to require it.

};
wizardContext.telemetry.properties.revisionMode = containerApp.revisionsMode;

if (isAzdExtensionInstalled()) {
Copy link
Member

Choose a reason for hiding this comment

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

Why is this being added here? Doesn't seem to be related to the PR?

Copy link
Contributor Author

@MicroFish91 MicroFish91 Jan 8, 2025

Choose a reason for hiding this comment

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

Yeah not crucial to this PR at all, but it was small enough that I snuck it in. It was in the same snippet as the output logs code section

);

// Log resource group
wizardContext.activityChildren?.push(
Copy link
Member

Choose a reason for hiding this comment

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

I feel like it might be time to make a utility function to just generate all of this boilerplate for you.

If not a util function, maybe include adding these activity children when you call pickContainerApp or pickManagedEnvironment? Since that seems to be where you are setting all of the wizard's contexts.

I feel like just adding them into the prompt steps themselves would be the best way to do it, but since these are top-level Azure resources, that might not be possible?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh interesting, I hadn't thought about doing it that way, but that might be a clean way to handle this boilerplate. I'll investigate that as a potential solution.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I consolidated most of the boilerplate under a new starting resource log step, let me know if you like that implementation or think it should be encapsulated differently!

Copy link
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.

Definitely less concerned about StartingResourcesLogStep since it's always set to false for shouldPrompt 👍

Base automatically changed from mwf/fiscal-beige to main January 10, 2025 01:32
@MicroFish91 MicroFish91 merged commit 3781ae6 into main Jan 10, 2025
2 checks passed
@MicroFish91 MicroFish91 deleted the mwf/obliged-gold branch January 10, 2025 01:59
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.

2 participants