607 Commits (8c7475d95e4de1c05d4aef5bcbde5a51ed4cdf08)

Author	SHA1	Message	Date
John Cowen	f7b8df281b	ui: Add `Service.Namespace` variable to dashboard URL templates (#11640) ... We currently allow only Datacenter, Service.Name, this PR adds Service.Namespace.	3 years ago
John Cowen	3f131dcf34	ui: Notifications re-organization/re-style (#11577) ... - Moves where they appear up to the <App /> component. - Instead of a <Notification /> wrapping component to move whatever you use for a notification up to where they need to appear (via ember-cli-flash), we now use a {{notification}} modifier now we have modifiers. - Global notifications/flashes are no longer special styles of their own. You just use the {{notification}} modifier to hoist whatever component/element you want up to the top of the page. This means we can re-use our existing <Notice /> component for all our global UI notifications (this is the user visible change here)	3 years ago
John Cowen	2b8273bc6e	ui: Support for SSO with Admin Partitions (#11604) ... * Upgrade AuthForm and document current state a little better * Hoist SSO out of the AuthForm * Bare minimum admin partitioned SSO also: ui: Tabbed Login with Token or SSO interface (#11619) - I upgraded our super old, almost the first ember component I wrote, to use glimmer/almost template only. This should use slots/contextual components somehow, but thats a bigger upgrade so I didn't go that far. - I've been wanting to upgrade the shape of our StateChart component for a very long while now, here its very apparent that it would be much better to do this sooner rather than later. I left it as is for now, but there will be a PR coming soon with a slight reshaping of this component. - Added a did-upsert modifier which is a mix of did-insert/did-update - Documentation added/amended for all the new things.	3 years ago
John Cowen	b84ee47ff0	ui: Fix brand coloring for inline-code plus docs (#11578) ... * ui: Fix brand coloring for inline-code plus docs Also use --tones instead of --black/--white (#11601) Co-authored-by: Evan Rowe <ev.rowe@gmail.com>	3 years ago
John Cowen	392dedc3e2	ui: Upgrades token sourcing related components to Glimmer+docs (#11592)	3 years ago
John Cowen	b4a7278e72	ui: Add eng docs for our render-template helper (#11359) ... Adds Engineer documentation for our recently improved render-template helper, plus some ideas for further work/improvement here should anyone ever want to pick that up.	3 years ago
John Cowen	b7bd938411	ui: Store the default partition when logging in (#11591) ... Make sure we store the default Partition for a users token.	3 years ago
John Cowen	35ccc2bc29	ui: Adding partitions + icons to upstreams/upstream instances (#11556) ... Adds a partition badge/label/visual to upstreams and upstream instances.	3 years ago
John Cowen	2ef9ea00b1	ui: When certain menus are selected reset either nspace/partition (#11479) ... For our dc, nspace and partition 'bucket' menus, sometimes when selecting one 'bucket' we need to reset a different 'bucket' back to the one that your token has by default (or the default if not). For example when switching to a different partition whilst you are in a non-default namespace of another partition, we need to switch you to the token default namespace of the partition you are switching to.	3 years ago
John Cowen	28b1e642cb	ui: Upstream CSS Tweaks (#11554) ... Various CSS tweaks/HTML cleanup around upstreams (but impacts other 'rows') - Prefer {{tooltip}} to <Tooltip> - Removed some now unnecessary spans - Stop using an empty class="" for styling purposes. - Renamed any classes used to identify response properties to follow the exact property name but kebab-cased. - Fixed up the alignment of things in the rows when used with a 'tiny copy button' (see screengrab) which was minus positioning and knocking things out (pending a proper refactor of our copy button CSS which is from the very very start of things)	3 years ago
John Cowen	c847c9a8cb	ui: Fixup partiton > partition typo (#11572)	3 years ago
Alessandro De Blasis	53a61349e1	ui: Fix code editor resizing and restyle (#11474) ... Fixes an issue where the code editor would not resizing to the full extent of the browser window plus CodeEditor restyling/refactoring - :label named block - :tools named block - :content named block - code and CSS cleanup - CodeEditor.mdx Signed-off-by: Alessandro De Blasis <alex@deblasis.net> Co-authored-by: John Cowen <johncowen@users.noreply.github.com>	3 years ago
John Cowen	6557f52962	ui: Bump our browser support (#11505) ... Bumps our browser support to a "rough ~2 years back" approach.	3 years ago
John Cowen	66f1dd9425	ui: [Port] Ensure the tokens default nspace (and partition) is passed thru to the auth endpoint (#11490) ... Most HTTP API calls will use the default namespace of the calling token to additionally filter/select the data used for the response if one is not specified by the frontend. The internal permissions/authorize endpoint does not do this (you can ask for permissions from different namespaces in on request). Therefore this PR adds the tokens default namespace in the frontend only to our calls to the authorize endpoint. I tried to do it in a place that made it feel like it's getting added in the backend, i.e. in a place which was least likely to ever require changing or thinking about. Note: We are probably going to change this internal endpoint to also inspect the tokens default namespace on the backend. At which point we can revert this commit/PR. * Add the same support for the tokens default partition	3 years ago
Kenia	37de276350	ui: Add Consul API Gateway as an external source (#11371)	3 years ago
John Cowen	537c4f32f7	Revert "Merge pull request #11328 from radiantly/ui/feature/allow-${}-style-interpolation" ... This reverts commit cd55c0cda3, reversing changes made to 14af8cb7a9.	3 years ago
John Cowen	aeaa0a6c96	ui: Temporarily force all UI capabilities (#11520) ... Temporarily revert to pre-1.10 UI functionality by overwriting frontend permissions. These are used to hide certain UI elements, but they are still enforced on the backend. This temporary measure should be removed again once https://github.com/hashicorp/consul/issues/11098 has been resolved	3 years ago
John Cowen	1515c3e667	ui: Filter global intentions list by selected partition (#11475) ... * ui: Filter global intentions list by namespace and partition Filters global intention listing by the current partition rather than trying to use a wildcard.	3 years ago
Kenia	4c2fa322a1	ui: Topology view with no dependencies (#11280)	3 years ago
John Cowen	25961355c1	ui: Only show partition / partition selector if enabled (#11484) ... I missed that partitions should never display if you can't use them, not just if you can't choose them.	3 years ago
John Cowen	72be2dd204	ui: Ensure we check intention service prefix permissions for per service (#11409) ... Port of: Ensure we check intention service prefix permissions for per service (#11270) Previously, when showing some action buttons for 'per service intentions' we used a global 'can I do something with any intention' permission to decide whether to show a certain button or not. If a user has a token that does not have 'global' intention permissions, but does have intention permissions on one or more specific services (for example via service / service_prefix), this meant that we did not show them certain buttons required to create/edit the intentions for this specific service. This PR adds that extra permissions check so we now check the intentions permissions per service instead of using the 'global' "can I edit intentions" question/request. **Notes:** - If a HTML button is `disabled` this means tippy.js doesn't adopt the popover properly and subsequently hide it from the user, so aswell as just disabling the button so you can't active the popover, we also don't even put the popover on the page - If `ability.item` or `ability.item.Resources` are empty then assume no access **We don't try to disable service > right hand side intention actions here** Whether you can create intentions for a service depends on the _destination_ of the intention you would like to create. For the topology view going from the LHS to the center, this is straightforwards as we only need to know the permissions for the central service, as when you are going from the LHS to the center, the center is the _destination_. When going from the center to the RHS the _destination[s]_ are on the RHS. This means we need to know the permissions for potentially 1000s of services all in one go in order to know when to show a button or not. We can't realistically discover the permissions for service > RHS services as we'd have either make a HTTP request per right hand service, or potentially make an incredibly large POST request for all the potentially 1000s of services on the right hand side (more preferable to 1000s of HTTP requests). Therefore for the moment at least we keep the old functionality (thin client) for the middle to RHS here. If you do go to click on the button and you don't have permissions to update the intention you will still not be able to update it, only you won't know this until you click the button (at which point you'll get a UI visible 403 error) Note: We reversed the conditional here between 1.10 and 1.11 So this make 100% sense that the port is different here to 1.11	3 years ago
Luke Kysow	c61208146d	Use "Open dashboard" everywhere (#11406) ... Previously we had "Open metrics Dashboard" and "Configure metrics dashboard" in the topology cards and then we had "Open Dashboard" in the top nav when the dashboard was configured. Now we use "Open dashboard" and "Configure dashboard". This change was made for consistency in wording and casing. In addition, the dashboard could be used for metrics but also other dashboards so there's no need to scope it only to metrics. Also the config is: ```hcl ui_config { dashboard_url_templates } ``` Which does not mention metrics	3 years ago
John Cowen	76f5de1455	ui: Ensure dc selector correctly shows the currently selected dc (#11380) ... * ui: Ensure dc selector correctly shows the currently selected dc * ui: Restrict access to non-default partitions in non-primaries (#11420) This PR restricts access via the UI to only the default partition when in a non-primary datacenter i.e. you can only have multiple (non-default) partitions in the primary datacenter.	3 years ago
John Cowen	b96794401f	ui: Add initial "How 2 Test UI" docs (#11296) ... Attempt to document out what a beginner to the project needs to know here in order to get started quickly Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>	3 years ago
John Cowen	86c88cc43a	ui: Ensure we provide an id for filtering policy-tokens (#11311)	3 years ago
Chris S. Kim	76bbeb3baf	ui: Pass primary dc through to uiserver (#11317) ... Co-authored-by: John Cowen <johncowen@users.noreply.github.com>	3 years ago
Jared Kirschner	cd55c0cda3	Merge pull request #11328 from radiantly/ui/feature/allow-${}-style-interpolation ... ui: Allow ${ } interpolation for UI Dashboard template URLs	3 years ago
John Cowen	e938e0afe0	ui: Remove remaining partition FIXME comments (#11312)	3 years ago
cooleditphoto	f801662f5c	ui: Topology metrics view outbound bytes color blue (#11343)	3 years ago
radiantly	fd51b3e76e	ui: Allow ${} interpolation for template URLs	3 years ago
John Cowen	a1a0ce1dad	ci: Only install UI dependencies for CI frontend-cache (#11313)	3 years ago
John Cowen	79b53ab23a	ui: Move the Role remove dialog to use InformedAction (#11298)	3 years ago
John Cowen	585f78f35a	ui: Fixup route blueprint to reflect project conventions (#11153)	3 years ago
Kenia	daec73e76c	ui: Topology - Fix up Default Allow and Permissive Intentions notices (#11216) ... * ui: Default allow notices test (#11240)	3 years ago
DillonStreator	03bc755162	ui: consistent empty state for intentions (#11261)	3 years ago
John Cowen	ed6918c6c2	ui: Improve dev-time SSO/OIDC visibility (#11248) ... This commit tries to make the development experience of working on our OIDC support a little more realistic, essentially by creating our own OIDC provider in our application (only during development builds). You can still provide a real OIDC provider to work with via our dev time environment/cookie variables as before, just now we default to the behaviour in this commit. Overall this makes it much easier to verify our OIDC support in the UI, and also opens up avenues for us to be able to test more scenarios that we couldn't before (for example not only successful logins, but also erroneous, potentially with multiple error reasons).	3 years ago
John Cowen	26c9d5c135	ui: Ignore erroneous ember/jQuery eslint warnings (#11238)	3 years ago
John Cowen	e5a15fdaac	ci: Don't focus install JS deps (#11267)	3 years ago
John Cowen	ebc8cbf957	ui: Fix up socket icon (#11234)	3 years ago
John Cowen	1cf008296d	docs: Fixes a typo in the UI readme docs (#11268)	3 years ago
Kenia	fca0e117e5	ui: Instructions for branch naming pattern (#11256) ... * Instructions for branch naming pattern * fix	3 years ago
John Cowen	baa377ddca	ui: Adds initial CRUD for partitions (#11188) ... * Add `is` and `test` helpers in a similar vein to `can` Adds 2 new helpers in a similar vein to ember-cans can: - `is` allows you to use vocab/phrases such as (is "something model") which calls isSomething() on the models ability. - `test` allows you to use vocab/phrases such as (test "is something model") or (test "can something model")which calls isSomething() / canSomething() on the models ability. Mostly using the is helper and the can helper. It's basically the is/can helper combined. * Adds TextInput component + related modifiers/helpers/machines/services (#11189) Adds a few new components/modifiers/helpers to aid building forms. - state-chart helper, used in lieu of a more generic approach for requiring our statecharts. - A few modifications to our existing disabled modifier. - A new 'validation' modifier, a super small form validation approach built to make use of state charts (optionally). Eventually we should be able to replace our current validation approach (ember-changeset-validations + extra deps) with this. - A new TextInput component, which is the first of our new components specifically to make it easy to build forms with validations. This is still a WIP, I left some comments in pointing out where this one would be progressed, but as we don't need the planned functionality yet, I left it where it was. All of this will be fleshed out more at a later date. Documentation is included for all of ^ * ui: Adds initial CRUD for partitions (#11190) Adds basic CRUD support for partitions. Engineering-wise probably the biggest takeaway here is that we needed to write very little javascript code to add this entire feature, and the little javascript we did need to write was very straightforwards. Everything is pretty much just HTML. Another note to make is that both ember-changeset and ember-data (model layer things) are now completely abstracted away from the view layer of the application. New components: - Consul::Partition::Form - Consul::Partition::List - Consul::Partition::Notifications - Consul::Partition::SearchBar - Consul::Partition::Selector See additional documentation here for more details New Route templates: - index.hbs partition listing/searching/filtering - edit.hbs partition editing and creation Additionally: There is some additional debug work here for better observability and to prevent any errors regarding our href-to usage when a dc is not available in our documentation site. Our softDelete functionality has been DRYed out a little to be used across two repos. isLinkable was removed from our ListCollection component for lists like upstream and service listing, and instead use our new is helper from within the ListCollection, meaning we've added a few more lighterweight templateOnly components. * ui: Exclude all debug-like files from the build (#11211) This PR adds **/*-debug.* to our test/prod excluded files (realised I needed to add test-support.js also so added that here as its more or less the same thing). Conditionally juggling ES6 static imports (specifically debug ones) for this was also getting a little hairy, so I moved it all to use the same approach as our conditional routes. All in all it brings the vendor build back down to ~430kb gzipped.	3 years ago
John Cowen	b8166de30d	ui: Replaces almost all remaining instances of SASS variables with CSS (#11200) ... From an engineers perspective, whenever specifying colors from now on we should use the form: ``` color: rgb(var(--tone-red-500)); ``` Please note: - Use rgb. This lets us do this like rgb(var(--tone-red-500) / 10%) so we can use a 10% opacity red-500 if we ever need to whilst still making use of our color tokens. - Use --tone-colorName-000 (so the prefix tone). Previously we could use a mix of --gray-500: $gray-500 (note the left hand CSS prop and right hand SASS var) for the things we need to theme currently. As we no longer use SASS we can't do --gray-500: --gray-500, so we now do --tone-gray-500: --gray-500. Just for clarity after that, whenever specifying a color anywhere, use rgb and --tone. There is only one reason where you might not use tone, and that is if you never want a color to be affected by a theme (for example a background shadow probably always should use --black) There are a 2 or 3 left for the code editor, plus our custom-query values	3 years ago
John Cowen	a9fe39e035	ui: Fix up blocking reconciliation for multiple models (#11237) ... > In the future, this should all be moved to each individual repository now, which will mean we can finally get rid of this service. This PR moves reconciliation to 'each individual repository'. I stopped short of getting rid of the service, but its so small now we pretty much don't need it. I'd rather wait until I look at the equivalent DataSink service and see if we can get rid of both equivalent services together (this also currently dependant on work soon to be merged) Reconciliation of models (basically doing the extra work to clean up the ember-data store and bring our frontend 'truth' into line with the actual backend truth) when blocking/long-polling on different views/filters of data is slightly more complicated due to figuring out what should be cleaned up and what should be left in the store. This is especially apparent for KVs. I built in a such a way to hopefully make sure it will all make sense for the future. I also checked that this all worked nicely with all our models, even KV which has never supported blocking queries. I left all that work in so that if we want to enable blocking queries/live updates for KV it now just involves deleting a couple of lines of code. There is a tonne of old stuff that we can clean up here now (our 'fake headers' that we pass around) and I've added that to my list of thing for a 'Big Cleanup PR' that will remove lots of code that we no longer require.	3 years ago
John Cowen	8b002d086a	ui: Address some Admin Partition FIXMEs (#11057) ... This commit addresses some left over admin partition FIXMEs 1. Adds Partition correctly to Service Instances 2. Converts non-important 'we can do this later' FIXMEs to TODOs 3. Removes some FIXMEs that I've double checked and addressed. Most of the remaining FIXMEs I'm waiting on responses to questions from the consul core folks for. I'll address those in a separate PR.	3 years ago
Kenia	5e7ef183ea	ui: Use of header default ACL policy (#11192) ... * Use of header default ACL policy * Update test for dc serializer	3 years ago
John Cowen	35a92e856b	ui: Make it hard to not URLEncode DataSource srcs/URIs (#11117) ... Our DataSource came in very iteratively, when we first started using it we specifically tried not to use it for things that would require portions of the @src="" attribute to be URL encoded (so things like service names couldn't be used, but dc etc would be fine). We then gradually added an easy way to url encode the @src="" attributes with a uri helper and began to use the DataSource component more and more. This meant that some DataSource usage continued to be used without our uri helper. Recently we hit #10901 which was a direct result of us not encoding @src values/URIs (I didn't realise this was one of the places that required URL encoding) and not going back over things to finish things off once we had implemented our uri helper, resulting in ~half of the codebase using it and ~half of it not. Now that almost all of the UI uses our DataSource component, this PR makes it even harder to not use the uri helper, by wrapping the string that it requires in a private URI class/object, that is then expected/asserted within the DataSource component/service. This means that as a result of this PR you cannot pass a plain string to the DataSource component without seeing an error in your JS console, which in turn means you have to use the uri helper, and it's very very hard to not URL encode any dynamic/user provided values, which otherwise could lead to bugs/errors similar to the one mentioned above. The error that you see when you don't use the uri helper is currently a 'soft' dev time only error, but like our other functionality that produces a soft error when you mistakenly pass an undefined value to a uri, at some point soon we will make these hard failing "do not do this" errors. Both of these 'soft error' DX features have been used this to great effect to implement our Admin Partition feature and these kind of things will minimize the amount of these types of bugs moving forwards in a preventative rather than curative manner. Hopefully these are the some of the kinds of things that get added to our codebase that prevent a multitude of problems and therefore are often never noticed/appreciated. Additionally here we moved the remaining non-uri using DataSources to use uri (that were now super easy to find), and also fixed up a place where I noticed (due to the soft errors) where we were sometimes passing undefined values to a uri call. The work here also led me to find another couple of non-important 'bugs' that I've PRed already separately, one of which is yet to be merged (#11105), hence the currently failing tests here. I'll rebase that once that PR is in and the tests here should then pass 🤞 Lastly, I didn't go the whole hog here to make DataSink also be this strict with its uri usage, there is a tiny bit more work on DataSink as a result of recently work, so I may (or may not) make DataSink equally as strict as part of that work in a separate PR.	3 years ago
John Cowen	7a5f335b7c	ui: Adds Flight icons to our icon set (#11097) ... * ui: Adds Flight icons to our icon set This commit doesn't actually add anything to the UI, rather just makes the flight icons available for use.	3 years ago
John Cowen	5e34d89f7f	ui: Hide create buttons for policies/roles/namespaces with readonly access (#10914) ... This PR adds a check to policy, role and namespace list pages to make sure the user has can write those things before offering to create them via a button. (The create page/form would then be a read-only form)	3 years ago
John Cowen	bce724baf1	ui: Don't show the CRD menu for read-only intentions (#11149) ... * ui: Don't show the CRD menu for read-only intentions The UI bug here manifests itself only when a user/token is configured to have read-only access to intentions. Instead of only letting folks click to see a read only page of the intention, we would show an additional message saying that the intention was read-only due to it being 'Managed by [a kubernetes] CRD'. Whilst the intention was still read only, this extra message was still confusing for users. This PR fixes up the conditional logic and further moves the logic to use ember-can - looking at the history of the files in question, this bug snuck itself in partly due to it being 'permission-y type stuff' previous to using ember-can and when something being editable or not was nothing to do with ACLs. Then we moved to start using ember-can without completely realising what IsEditable previously meant. So overall the code here is a tiny bit clearer/cleaner by adding a proper can view CRD intention instead of overloading the idea of 'editability'.	3 years ago