ec369f58 Merge pull request #153 from dholbach/drop-email
ef7418d3 weave-users mailing list is closed: https://groups.google.com/a/weave.works/forum/#!topic/weave-users/0QXWGOPdBfY
6954a578 Merge pull request #144 from weaveworks/golang-1.11.1
9649eed1 Upgrade build image from golang:1.10.0-strech to 1.11.1-strech
59263a71 Merge pull request #141 from weaveworks/update-context
e235c9b0 Merge pull request #143 from weaveworks/gc-wks-test-vms
c865b4cc scheduler: please lint/flake8
da61568d scheduler: please lint/yapf
ce9d78e3 scheduler: do not cache discovery doc
e4b78733 scheduler: add comment about GCP projects' IAM roles needed to list/delete instances and firewall rules
ff7ec8e6 scheduler: add comment about CircleCI projects' access via the API
2477d98c scheduler: deploy command now sets the current datetime as the version
5fcd8809 scheduler: pass CircleCI API token in for private projects
6b8c3231 scheduler: more details in case of failure to get running builds from CircleCI
0871aff8 scheduler: downgrade google-api-python-client from 1.7.4 to 1.6.7
b631e7f1 scheduler: add GC of WKS test VMs and firewall rules
a923a320 scheduler: document setup and deployment
013f5082 scheduler: lock dependencies' versions
6965a4a4 Merge pull request #142 from weaveworks/fix-build
23298c6f Fix golint expects import golang.org/x/lint/golint
482f4cd0 Context is now part of the Go standard library
git-subtree-dir: tools
git-subtree-split: ec369f58d7ac85375bad7d0f02a1462cdad290f9
- Renames placeholders `:orgId` to `:instanceId` in
`--app.metrics-graph`
- Adjusts frontend client to use the provided instanceId by its host
application (Weave Cloud)
- Name of the PVC can be same in different namespaces, in this
scenario an application pod is connected to multiple PVC.
Signed-off-by: Akash Srivastava <akashsrivastava4927@gmail.com>
@fbarl and I talked about having a FAQ doc for Scope, where we can list
tid-bits of information to work with Scope.
Started off the doc with a piece that was discussed in #3406.
Signed-off-by: Daniel Holbach <daniel@weave.works>
This avoids side-effects from reporting Kubernetes from a
cluster-level probe, and removes a lie from the probe data.
Rather than do the work every time the probe sends a report, we do it
every time the app renders endpoints, which should be once per merged
report set.
