Update core.yaml

# About
This description was generated using this script:
```sh
#!/bin/bash
set -e
GHORG=${GHORG:-fabric8-services}
GHREPO=${GHREPO:-fabric8-wit}
cat <<EOF
# About
This description was generated using this script:
\`\`\`sh
`cat $0`
\`\`\`
Invoked as:

    `echo GHORG=${GHORG} GHREPO=${GHREPO} $(basename $0) ${@:1}`

# Changes
EOF
git log \
  --pretty="%n**Commit:** https://github.com/${GHORG}/${GHREPO}/commit/%H%n**Author:** %an (%ae)%n**Date:** %aI%n%n%s%n%n%b%n%n----%n" \
  --reverse ${@:1} \
  | sed -E "s/([\s|\(| ])#([0-9]+)/\1${GHORG}\/${GHREPO}#\2/g"
```
Invoked as:

    GHORG=fabric8-services GHREPO=fabric8-wit git-log-pr.sh 164762f67a3a7634fa4ee1e8bb55c458281803c7..upstream/master

# Changes

**Commit:** fabric8-services/fabric8-wit@7ab24ac
**Author:** Tina Kurian (tkurian@redhat.com)
**Date:** 2018-09-10T09:47:29-04:00

area iteration root path should not be empty (fabric8-services/fabric8-wit#2214)

See fabric8-services/fabric8-wit#2203

Co-authored-by: Konrad Kleine 193408+kwk@users.noreply.github.com

----


**Commit:** fabric8-services/fabric8-wit@c2816aa
**Author:** Ibrahim Jarif (jarifibrahim@gmail.com)
**Date:** 2018-09-10T21:47:14+05:30

Update gopkg.lock file (fabric8-services/fabric8-wit#2282)

The `gopkg.lock` file is out of date. This PR updated it.


How to verify this PR
1. Run `dep ensure` on current master. You should see the `gopkg.lock` is modified.
2. Check the changes in `gopkg.lock` file against the ones in this PR. They should be same.
3. Run `dep ensure` again and you would notice `gopkg.lock` has not changed.

----


**Commit:** fabric8-services/fabric8-wit@426e11b
**Author:** Elliott Baron (ebaron@redhat.com)
**Date:** 2018-09-10T16:29:27-04:00

Add authorization checking to Kubernetes package (fabric8-services/fabric8-wit#2207)

* Initial implementation of OpenShift authz checking

* Remove unused interactions in delete cassettes

* Add CanDeploy to filter deployable environments, maintain full list in kubeClient

* Implement authz check for DeleteDeployment

* Implement remaining methods, add tests for access control failure on builds

* Fix URLProvider changes, add tests for CanDeploy

* Better test error conditions

* Clean up code

* Add more internal environments to kubeclient tests

* Improve documentation, avoid boolean parameter for getting namespace

* Also check for wildcard rules

* Reduce size of go-vcr cassettes


----


**Commit:** fabric8-services/fabric8-wit@a8fab53
**Author:** Konrad Kleine (193408+kwk@users.noreply.github.com)
**Date:** 2018-09-11T08:37:08+02:00

testfixture.GetTestFileAndFunc() (fabric8-services/fabric8-wit#2149)

`GetTestFileAndFunc` returns the file and function of the first `_test.go` file to appear in the stack and returns it in this schema:

```
(see function github.com/fabric8-services/fabric8-wit/test/testfixture_test.TestGetGetTestFileAndFunc in test/testfixture/testfixture_test.go)
```

The result can be used to augment entities so that we always can tell which test created an entity that is a left-over and not cleaned up for example.

NOTE: The `testfixutre.GetTestFileAndFunc()` was taken out of this PR and already merge with this PR fabric8-services/fabric8-wit#2214. It is no longer part of this PR.

Most of the entities created with the `test/testfixture` package now contain a description that reveals in which function the entities was created. When there are left-over entities that hinder tests from running properly, you can now go in the database and find out which test produced these left-overs. To simplify things when running on CI, we now output a list of remaining spaces automatically that looks like this if everything went ok:

```
Check that no unexpected left-over spaces exist after running tests:

-[ RECORD 1 ]-------------------------------------

id          | 2e0698d8-753e-4cef-bb7c-f027634824a2

name        | system.space

description | Description of the space
```

Note, that the `system.space` is okay to appear in this list. It is expected even though it should go away at some point.

See fabric8-services/fabric8-wit#2278 for an example of a PR that was easily fixed because of this PR. 

----


**Commit:** fabric8-services/fabric8-wit@ba71ed1
**Author:** Konrad Kleine (193408+kwk@users.noreply.github.com)
**Date:** 2018-09-11T12:14:39+02:00

Allow searching for work items with a single quote in the search string (fabric8-services/fabric8-wit#2272)

A query parameter `q` as in `https://prod-preview.openshift.io/api/search?q='problem` was not properly escaped before it was passed to the PostgreSQL `to_tsquery` function. We now remove the single quote from the input to `to_tsquery`.

On the frontend this API was called when search for work items in the "Links" section.

Addresses fabric8-services/fabric8-wit#2273 and openshiftio/openshift.io#4288


----


**Commit:** fabric8-services/fabric8-wit@d6a192d
**Author:** Konrad Kleine (193408+kwk@users.noreply.github.com)
**Date:** 2018-09-11T12:50:30+02:00

Don't run tests involving the DB in parallel (fabric8-services/fabric8-wit#2276)

Possibly related to openshiftio/openshift.io#4299

----


**Commit:** fabric8-services/fabric8-wit@f276f3a
**Author:** Konrad Kleine (193408+kwk@users.noreply.github.com)
**Date:** 2018-09-17T14:30:48+02:00

Don't have a zero-parent relationship for root iteration/area (fabric8-services/fabric8-wit#2283)

Before a root iteration/area had a parent iteration with a zeroed UUID:

```yaml
"relationships": {
      "parent": {
        "data": {
          "id": "00000000-0000-0000-0000-000000000000",
          "type": "iterations"
        },
```

That is removed now.

This adds a test that shows how a root and a child iteration/area are represented on JSONAPI level.

Added `testfixture.SetAreaNames()` and `testfixture.AreaByName()` functions as well.

This fixes the root cause for openshiftio/openshift.io#4309 . The UI fix in Raunak1203/fabric8-planner@e7c34a2 only fixes a symptom by implementing a work around.
----


**Commit:** fabric8-services/fabric8-wit@59561d0
**Author:** Ibrahim Jarif (jarifibrahim@gmail.com)
**Date:** 2018-09-17T18:38:35+05:30

Better error logging for Delete action on /space endpoint (fabric8-services/fabric8-wit#2280)

----

dsaas-services/core.yaml

@@ -1,5 +1,5 @@
 services:
-- hash: 164762f67a3a7634fa4ee1e8bb55c458281803c7
+- hash: 59561d074d5bc6574994b4821db0bff0278fa010
   name: fabric8-wit
   path: /openshift/core.app.yaml
   url: https://github.com/fabric8-services/fabric8-wit/