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

[ui] Service Discovery: Allocation Service fly-out #14389

Conversation

philrenaud
Copy link
Contributor

@philrenaud philrenaud commented Aug 29, 2022

resolves #14386

Establishes a sidebar component with queryParam persistence.

Side-effect

  • Adds the concept of a refID to service fragments for easier lookup. They already have a TaskName property, and added a GroupName property as well.

@github-actions
Copy link

github-actions bot commented Aug 29, 2022

Ember Asset Size action

As of 3780255

Files that got Bigger 🚨:

File raw gzip
nomad-ui.js +8.16 kB +1.42 kB
nomad-ui.css +713 B +213 B

Files that stayed the same size 🤷‍:

File raw gzip
vendor.js 0 B 0 B
vendor.css 0 B 0 B

@github-actions
Copy link

github-actions bot commented Aug 29, 2022

Ember Test Audit comparison

f-ui/service-discovery 3780255 change
passes 1425 1427 +2
failures 0 0 0
flaky 0 0 0
duration 11m 38s 477ms 10m 05s 968ms -1m 32s 509ms

@philrenaud philrenaud changed the title [ui] Service Discovery: Allocation Service Detail View [ui] Service Discovery: Allocation Service fly-out Aug 30, 2022
Comment on lines +1 to +2
$topNavOffset: 112px;
$subNavOffset: 49px;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Making these variables to avoid magic-number syndrome

Comment on lines 11 to 15
if (hash.Services) {
hash.Services.forEach((service) => {
service.GroupName = hash.Name;
});
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

not needed in the task serializer, as services there already get populated with TaskName props.

@philrenaud philrenaud marked this pull request as ready for review September 1, 2022 16:04
Copy link
Contributor

@ChaiWithJai ChaiWithJai left a comment

Choose a reason for hiding this comment

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

LGTM

ui/app/components/evaluation-sidebar/detail.js Outdated Show resolved Hide resolved
ui/app/components/service-status-bar.js Show resolved Hide resolved
ui/app/controllers/allocations/allocation/index.js Outdated Show resolved Hide resolved
ui/app/models/service-fragment.js Outdated Show resolved Hide resolved
ui/app/templates/allocations.hbs Outdated Show resolved Hide resolved
@philrenaud philrenaud merged this pull request into f-ui/service-discovery Sep 7, 2022
@philrenaud philrenaud deleted the 14386-ui-service-discovery-service-fly-out-detail-view branch September 7, 2022 14:23
philrenaud added a commit that referenced this pull request Sep 7, 2022
* Bones of a new flyout section

* Basic sidebar behaviour and style edits

* Concept of a refID for service fragments to disambiguate task and group

* A11y audit etc

* Moves health check aggregation to serviceFragment model and retains history

* Has to be a getter

* flyout populated

* Sidebar styling

* Sidebar table and details added

* Mirage fixture

* Active status and table styles

* Unit test mock updated

* Acceptance tests for alloc services table and flyout

* Chart styles closer to mock

* Without a paused test

* Consul and Nomad icons in services table

* Alloc services test updates in light of new column changes

* without using an inherited scenario
@github-actions
Copy link

github-actions bot commented Jan 6, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants