open-consul/ui/packages/consul-ui/app/models/discovery-chain.js

23 lines
805 B
JavaScript
Raw Normal View History

import Model, { attr } from '@ember-data/model';
ui: Discovery Chain (#6746) * Add data layer for discovery chain (model/adapter/serializer/repo) * Add routing plus template for routing tab * Add extra deps - consul-api-double upgrade plus ngraph for graphing * Add discovery-chain and related components and helpers: 1. discovery-chain to orchestrate/view controller 2. route-card, splitter-card, resolver card to represent the 3 different node types. 3. route-match helper for easy formatting of route rules 4. dom-position to figure out where things are in order to draw lines 5. svg-curve, simple wrapper around svg's <path d=""> attribute format. 6. data-structs service. This isn't super required but we are using other data-structures provided by other third party npm modules in other yet to be merged PRs. All of these types of things will live here for easy access/injection/changability 7. Some additions to our css-var 'polyfill' for a couple of extra needed rules * Related CSS for discovery chain 1. We add a %card base component here, eventually this will go into our base folder and %stats-card will also use it for a base component. 2. New icon for failovers * ui: Discovery Chain Continued (#6939) 1. Add in the things we use for the animations 2 Use IntersectionObserver so we know when the tab is visible, otherwise the dom-position helper won't work as the dom elements don't have any display. 3. Add some base work for animations and use them a little 4. Try to detect if a resolver is a redirect. Right now this works for datacenters and namespaces, but it can't work for services and subsets - we are awaiting backend support for doing this properly. 5. Add a fake 'this service has no routes' route that says 'Default' 6. redirect icon 7. Add CSS.escape polyfill for Edge
2019-12-17 19:27:28 +00:00
export const PRIMARY_KEY = 'uid';
export const SLUG_KEY = 'ServiceName';
export default class DiscoveryChain extends Model {
@attr('string') uid;
@attr('string') ServiceName;
@attr('string') Datacenter;
// Whilst the disco chain itself is scoped to a ns/partition we generally only
// use data from within the disco chain itself when displaying data (i.e. the
// configs themselves) We also use the API response JSON for fingerprinting
// already. All in-all these properties are mainly here for consistency rather
// than need as of writing in case any assumptions are made expecting disco
// chain root Partition/Namespace
@attr('string') Partition;
@attr('string') Namespace;
//
@attr() Chain; // {}
@attr() meta; // {}
}