John Cowen 327aac9fe9
ui: Acceptance test improvements to prepare for more NS tests (#6980)
* ui: Acceptance test improvements to prepare for more NS tests

* ui: Namespace acceptance testing (#7005)

* Update api-double and consul-api-double for http.body

* Adds places where we missed passing the nspace through

* Hardcode nspace CRUD to use the default nspace for policies and roles

* Alter test helpers to allow us to control nspaces from the outside

* Amends to allow tests to account for namespace, move ns from queryParam

1. We decided to move how we pass the namespace value through to the
backend when performing write actions (create, update). Previoulsy we
were using the queryParam although using the post body is the preferred
method to send the Namespace details through to the backend.
2. Other various amends to take into account testing across multiple
namespaced scenarios

* Enable nspace testing by default

* Remove last few occurances of old style http assertions

We had informally 'deprecated' our old style of http assertions that
relied on the order of http calls (even though that order was not
important for the assertion). Following on from our namespace work we
removed the majority of the old occrances of these old style assertions.

This commit removes the remaining few, and also then cleans up the
assertions/http.js file to only include the ones we are using.

This reduces our available step count further and prevents any confusion
over the usage of the old types and the new types.

* ui: Namespace CRUD acceptance tests (#7016)

* Upgrade consul-api-double

* Add all the things required for testing:

1. edit and index page objects
2. enable CONSUL_NSPACE_COUNT cookie setting
3. enable mutating HTTP response bodies based on URL

* Add acceptance test for nspace edit/delete/list and searching
2020-01-24 12:26:28 +00:00

51 lines
2.4 KiB
Handlebars

<form>
{{role-form form=form item=item dc=dc nspace=nspace}}
{{#if (and (not create) (gt items.length 0))}}
<h2>Where is this role used?</h2>
<p>
We're only able to show information for the primary datacenter and the current datacenter. This list may not show every case where this role is applied.
</p>
{{token-list caption="Tokens" items=items}}
{{/if}}
<div>
{{#if create }}
{{! we only need to check for an empty name here as ember munges autofocus, once we have autofocus back revisit this}}
<button type="submit" {{ action "create" item}} disabled={{if (or item.isPristine item.isInvalid (eq item.Name '')) 'disabled'}}>Save</button>
{{ else }}
<button type="submit" {{ action "update" item}} disabled={{if item.isInvalid 'disabled'}}>Save</button>
{{/if}}
<button type="reset" {{ action "cancel" item}}>Cancel</button>
{{# if (not create) }}
{{#confirmation-dialog message='Are you sure you want to delete this Role?'}}
{{#block-slot name='action' as |confirm|}}
<button type="button" data-test-delete class="type-delete" {{action confirm 'delete' item}}>Delete</button>
{{/block-slot}}
{{#block-slot name='dialog' as |execute cancel message|}}
{{#if (gt items.length 0)}}
{{#modal-dialog onclose=(action cancel)}}
{{#block-slot name='header'}}
<h2>Role in Use</h2>
{{/block-slot}}
{{#block-slot name='body'}}
<p>
This Role is currently in use. If you choose to delete this Role, it will be removed from the following <strong>{{items.length}} Tokens</strong>:
</p>
{{token-list items=items target='_blank'}}
<p>
This action cannot be undone. {{message}}
</p>
{{/block-slot}}
{{#block-slot name='actions' as |close|}}
<button type="button" class="type-delete" {{action execute}}>Yes, Delete</button>
<button type="button" class="type-cancel" {{action close}}>Cancel</button>
{{/block-slot}}
{{/modal-dialog}}
{{else}}
{{delete-confirmation message=message execute=execute cancel=cancel}}
{{/if}}
{{/block-slot}}
{{/confirmation-dialog}}
{{/if}}
</div>
</form>