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

Azure Web App name doesn't display when editing the step #3577

Closed
KennethBates opened this issue Jun 20, 2017 · 4 comments
Closed

Azure Web App name doesn't display when editing the step #3577

KennethBates opened this issue Jun 20, 2017 · 4 comments
Assignees
Labels
feature/usability kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@KennethBates
Copy link

Server: 3.14.1

When editing an existing Azure web app step, the web app name doesn't automatically get populated with the app that was already chosen for the step. The step still functions and deploys the correct app, and displays the name when selecting Use a custom expression - it's just a display issue.
Steps to reproduce -

  1. Create a Deploy an Azure Web App step and select an app
  2. Save the step
  3. Edit the same step - no app is auto-populated in display

Source: http://help.octopusdeploy.com/discussions/problems/55347

Previous issue: #2649

@KennethBates KennethBates added area/modelling kind/bug This issue represents a verified problem we are committed to solving feature/usability labels Jun 20, 2017
@slewis74
Copy link

Regression in AzureWebSitesListAction's AzureWebSite class. Looks like R# code cleanup got carried away and made ResourceGroup and WebSpace private because it couldn't see them being called (JSON serializer does but R# can't see that). Without those the Save loses data and the reload then won't select the item in the combo.

@MarkSiedle
Copy link

Bad Mark, good find Shannon 👍

@octoreleasebot
Copy link

Release Note: Azure Web App step correctly reloads the site list when editing

@lock
Copy link

lock bot commented Nov 24, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature/usability kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

4 participants