Closed kragniz closed 6 years ago
I've got mixed feelings about this.
kubectl get cassandra
kubectl get cass
at the start of the test would be sufficient.kubectl get cassandra
feels more natural and sets a precedent for how we shorten names in future (e.g. CouchbaseCluster
-> couchbase
) etc.
I'm not bothered about cass
too much, but it does seems to be an arbitrarily shortened version of cassandra
and isn't particularly obvious. wdyt @kragniz?
cass
was pretty random, I'm happy with cassandra
instead.
ping @kragniz
Updated with cassandra
and elasticsearch
shortnames
@kragniz: The following test failed, say /retest
to rerun them all:
Test name | Commit | Details | Rerun command |
---|---|---|---|
navigator-e2e-v1-10 | 06319c63669dcb029f828cff3da392926cc2b774 | link | /test e2e v1.10 |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: munnerz
The full list of commands accepted by this bot can be found here.
The pull request process is described here
So commands like
kubectl get cass
are shorter.