Gregor Riepl

I just had an idea how passing defaults to the (un)marshaller could work: In a structured type, add custom tags to the the fields. These could then be interpreted by...

I created a proposal on the Go issue tracker for such a feature: golang/go#21425

I played around a bit and tried to build a generic default value handler. But it's not easy. Go's reflection package is giving me headaches. Simple assignments like above will...

I tested out your approach, it works nicely. Special handling is still required for other field types than string and embedded types. Something like this: ```go type ActuateType string type...

An interesting idea... Another possible approach would be a simple constructor for each type that prefills fields with their default values. This may even avoid custom UnmarshalXML methods. Care must...

I actually went ahead and did already implement some of these. But I'm still struggling with a few other things related to the MPEG-DASH XSD I mentioned in #16. In...

As a workaround, you can use the `lifecycle` argument `replace_triggered_by`: ```terraform resource "openstack_networking_port_v2" "ns" { lifecycle { replace_triggered_by = [ openstack_networking_subnet_v2.ops ] } } ``` Requires Terraform 1.2+.

To get started, a rough outline: 1. Ensure a CCM for your cloud environment is available, with roughly the same feature set than the integrated KCM provider. Determine compatibility issues...

Yes, I think I can do that. But I will need more input, and possibly some insight on the situation with different providers. - Which features are likely to have...

And also, where should the documentation live? - on /docs/concepts/cluster-administration/cloud-providers.md ? - in a new page under /docs/concepts/cluster-administration/cloud-providers/ ? - in a new page under /docs/tasks/administer-cluster/ ? - in a...