ab06a22954
Merge pull request #4841 from hashicorp/f-ui-error-handling-on-all-pages
...
UI: Error handling on all pages
2018-11-07 11:16:06 -08:00
19abb7b605
Clean up the remaining routes
2018-11-05 16:33:33 -08:00
d4c6a698c3
Handle the job 404 error case on the other job sub pages
2018-11-05 16:06:08 -08:00
af24546644
Handle the job 404 error case in versions
2018-11-05 15:42:04 -08:00
2925285f00
Handle the job 404 case in the job definition route
2018-11-05 15:20:31 -08:00
8ef22a06fe
Handle the job 404 case in task group routes
2018-11-02 19:25:50 -07:00
7cd8179637
Test coverage for breadcrumb qp change
2018-10-31 13:27:35 -07:00
0a4242eb13
Provide the namespace query param to the task group link
2018-10-31 12:50:39 -07:00
1f40ab5da5
Introduce job editing to the job definition page
2018-08-21 16:46:24 -07:00
4d656c7a31
Parse and Plan API and UI workflows
2018-08-14 17:29:51 -07:00
b0939bde07
Add breadcrumb to the run job page
2018-08-14 13:06:26 -07:00
8ca806f8f8
Use the model hook and setupController hook instead of afterModel
...
This is a more idiomatic way to handle the QP resetting in the
application controller.
2018-08-13 16:18:06 -07:00
9f3a37f1c2
Simplify the control flow around changing namespaces and regions
...
The UI will no longer try to redirect to the appropriate namespace or
region if one is found in localStorage. Instead, it will assume that
the lack of query param means the default namespaces or region is
desired.
2018-08-09 18:22:39 -07:00
3180e57138
Only deal with the region param (in the app and in api calls) when necessary
2018-08-09 18:22:39 -07:00
c4c79c7a1f
Get the server's region (aka default region) from the API
...
The default region shouldn't be used as a qp since no qp means the same
thing.
2018-08-09 18:22:38 -07:00
d61fd9ef48
The application route doesn't need to fetch namespaces
2018-08-09 18:22:38 -07:00
ad70fb9cc3
Repeat the new namespace pattern for region
2018-08-09 18:22:38 -07:00
93f41278b1
Clear up the data flow for namespaces
...
This is incredibly tricky with query params, since there is a bundle of
timing issues, lifecycle issues, missing features, and all around
gotchas with query params.
This solution has no observers and no instances of the system service
being set from the jobs controller.
The upside to this is no observers, much easier to follow logic, no more
dependent key chain reactions.
2018-08-09 18:22:38 -07:00
b889c8091e
Fetch regions and namespaces in the application route
2018-08-09 18:22:37 -07:00
2bb770361b
Add three-way region property (query param, service, localStorage)
2018-08-09 18:22:37 -07:00
40826b2b88
Watch allocations on the job index page
...
Since there are no recent allocations, those alloc need to be watched
2018-08-06 11:02:21 -07:00
f6a3008d08
New dedicated allocations page for jobs
2018-08-06 10:59:35 -07:00
f0ab8a231f
Merge pull request #4533 from hashicorp/f-ui-refactor-page-chrome
...
UI: Refactor page chrome
2018-08-06 10:50:03 -07:00
0e7b8dc7d2
Get the latest deployment for a job by using the appropriate API
2018-07-30 15:24:31 -07:00
4e22c1018f
Redo onNamespaceChange to use the router
2018-07-30 13:13:52 -07:00
38b4d30272
Merge pull request #4458 from hashicorp/f-ui-refactor-breadcrumbs
...
UI: Refactor breadcrumbs
2018-07-10 11:01:28 -07:00
bbb923ea89
Initial evaluations page
2018-07-06 16:41:09 -07:00
a045db8ce4
Update tests to match new test selectors
2018-07-06 11:12:12 -07:00
b5b632068d
Use the new breadcrumb pattern on tasks
2018-07-06 11:12:11 -07:00
de89051438
Use the new breadcrumbs pattern for allocations
2018-07-06 11:12:11 -07:00
3bda577de7
Apply new breadcrumbs pattern to task groups
2018-07-06 11:12:11 -07:00
a4ff0c1040
Support namespaces in job breadcrumbs
2018-07-06 11:12:11 -07:00
f0ecc7d9c8
Add breadcrumbs to jobs routes
2018-07-06 11:12:11 -07:00
9bc1d0e4f4
Apply new breadcrumbs pattern to servers and clients
2018-07-06 11:12:11 -07:00
b7d833a5e0
Correctly watch the job summary on the task group page
...
It changed from being a relationship to a model
2018-03-28 15:12:27 -07:00
4c34a04151
Work around the dreaded broken relationship ED bug
...
Summary can unlink from a job when loaded in the wrong order. This
guarantees that the summary is bound to the job detail view by
falling back to the summary in the store.
2018-03-22 20:14:37 -07:00
810c5c3f7c
Perioidic and Parameterized jobs need to watch /jobs for child updates
2018-03-20 16:41:53 -07:00
8e9fe5df01
Deployments should only be watched when the job type supports deployments
2018-03-20 16:23:03 -07:00
53ee4d72a5
Make allocation pages extend the job breadcrumb trail
2018-03-13 16:36:26 -07:00
0cfa36d839
Don't let aborted requests redirect to error
2018-03-08 10:40:31 -08:00
314f1ea436
Change from the setupController hook to the new startWatchers hook
2018-03-08 10:40:31 -08:00
2282f3243a
Use willTransition instead of deactivate to cancel requests
...
deactivate happens _after_ the new route's model hook, which
results in the possibility of canceling new requests right
after they are made rather than existing open connections
2018-03-05 09:32:05 -08:00
83df67a8ab
Watch node and related allocations on the client detail page
2018-03-05 09:32:04 -08:00
e54cf51460
Move node watching to the index page
...
It doesn't need to impact the entire route hierarchy
2018-03-05 09:32:04 -08:00
5363f32d33
Watch the allocation on the allocation and task pages
2018-03-05 09:32:04 -08:00
c201d3ae8f
Watch job, job-summary, and job-allocs on the task group page
2018-03-05 09:32:04 -08:00
a79c0aa853
Move jobs polling from jobs to jobs.index
...
It's only necessary for the list view, not the entire route hierarchy
2018-03-05 09:32:04 -08:00
b1125c1a1f
Add polling to the deployments page
2018-03-05 09:32:04 -08:00
8b0ad9f2fb
Move job watchers to job.index
...
They are only for the overview page, not the whole hierarchy
2018-03-05 09:32:04 -08:00
2b6f07c4c3
Watch job versions
2018-03-05 09:32:03 -08:00
Michael Lange