Skip to content

Conversation

@redbaron
Copy link

With this change it is possible to install multiple
Grafanas into same namespace without clashing

Also DRY object references a bit

Based on #67

@redbaron redbaron force-pushed the customizable-name branch from 2e5e3d5 to 66d8387 Compare May 22, 2019 20:05
It seems that shape of the object produced by individual
jsonnet library agreed to be following:

```
{
  hidden:: { ... }

  component: {
    resource1: { apiVersion: ... , kind: .... },
    resource2: { apiVersion: ... , kind: .... },
  }
}
```

so that std.objectFields(obj) returns an object
made of kubernetes object to apply.

Hidden fields are then can be used for cooperation
on values, such as `_config::`

This commit brings produced output in line with convention above
@redbaron redbaron force-pushed the customizable-name branch 3 times, most recently from 202e4b3 to b907c6e Compare May 23, 2019 10:28
redbaron added 3 commits May 23, 2019 11:34
If there is no dashboards, then no /grafana-dashboard-definitions/0/
is created and Grafana becomes upset, because it's provisioning
config points there.
With this change it is possible to install multiple
Grafanas into same namespace without clashing
@redbaron redbaron force-pushed the customizable-name branch from b907c6e to 1c12c74 Compare May 23, 2019 10:35
@brancz
Copy link
Owner

brancz commented May 28, 2019

I generally like this a lot. Let's first get #67 resolved, then continue with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants