Mickaël Canévet
Mickaël Canévet
We'll unfortunately not have time to work on this in the next few weeks, but if someone want to propose a PR, we'll have a look at it. So no...
This provider talks to the Cattle v2-beta API, so maybe it should have been named `cattle` instead of `rancher`. I'm not sure there is still a "Cattle API" in Rancher2....
@raphink @cloudnautique ready to review.
@raphink could you please review this? The idea is to be able to deploy stack from a CI that would run on an environment without needing to pass credentials. For...
If it does not break what exists, yes.
@cloudnautique is there any documentation about the roles somewhere? Or do you know which role we would need to have Service Account keys that would allow to deploy a stack...
@cloudnautique my goal is to deploy a lightweight CI/CD in every environment (drone CI for example) so that my users can use it to deploy their stacks describe in Terraform...
According to @raphink the line who causes this is https://github.com/terraform-providers/terraform-provider-rancher/blob/master/rancher/config.go#L41. We may have to refactor the configuration to use in-cluster keys...
This is because you have to quote the numbers and booleans in your yaml file. I suppose that the yaml format has some automatic value typing and you have to...
Well in a way that makes sense. The boolean under the `volumes` key is really mapped to a boolean in the volume driver I guess, whereas boolean under the `labels`...