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

[release/8.0]: Backporting dashboard refactoring #3548

Merged
merged 4 commits into from
Apr 10, 2024

Conversation

davidfowl
Copy link
Member

@davidfowl davidfowl commented Apr 10, 2024

Backporting changes from main:

Customer Impact

Backporting improvements to how the dashboard is modeled in the app model along with other reliability fixes. There are other fixes in this PR to do with test reliability.

Testing

This change itself adds LOTS of test coverage we didn't have before. That was one of the main purposes of the refactoring.

Risk

Medium. This is a big refactoring, but it has been running in main for a couple of days and we have runway to fix issues (we fixed a couple already).

We have 2 other PRs coming that depend build on this change. There's risk in doing it differently in main and release/8.0.

Regression?

No

karolz-ms and others added 4 commits April 9, 2024 22:23
* Improve service address allocation
Should fix #3265
* Make the dashboard an appmodel resource

- Moved dashboard resource into a lifecycle hook instead of making it a dcp resource.
This removes the specialized code from ApplicationExecutor from knowing about the dashboard.
As a result of this change I also cleaned up how we configure and validate dcp options to use IConfigureOptions and IValidateOptions.
- Added tests for the dashboard resource
- Made a change to ApplicationExecutor to allow resources that start as
hidden to remain hidden.
- Added hidden to a new known resource states class
- Added more test cases
* Only add dashboard services if the dashboard is enabled
#3472)

- Print it right after we print the dashboard url
- Refactored the dashboard resource to use DashboardOptions instead of DcpOptions
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-codeflow for labeling automated codeflow. intentionally a different color! label Apr 10, 2024
@dotnet-policy-service dotnet-policy-service bot added the Servicing-consider Issue for next servicing release review label Apr 10, 2024
@danmoseley danmoseley added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Apr 10, 2024
Copy link
Member

@joperezr joperezr left a comment

Choose a reason for hiding this comment

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

Approved in chat.

@joperezr joperezr merged commit a4cf987 into release/8.0 Apr 10, 2024
8 checks passed
@joperezr joperezr deleted the davidfowl/bp-dashboard-refactor branch April 10, 2024 20:27
@danmoseley danmoseley mentioned this pull request Apr 12, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-codeflow for labeling automated codeflow. intentionally a different color! Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants