The problem here is, we cannot really offer a transition path to the users. We can warn that it will break and then.. what? I have to continue using non-singleton until upstream switched to…
@nico Hm... what if we can support positional parameter for singleton types? It wouldn't be object id but plain positional parameter, optional. It's just that we would need to support it with some…
So there would only be one positional argument allowed and only for singleton types?
I know, it's kind of a hack, but there is already only one positional argument allowed for non-singleton types, and that's object id.
With singleton types you cannot call it object id, since there can be only one singleton type object.
When I think more about it we shouldn't hack singleton type core support. But we should decide on the way of deprecation and replacing the old one with the new one.
What's about to only use it while the non-singleton type is deprecated? So you can map the object id to one parameter. Then, every time the singleton type will be called as a normal object, it will…
No, I thought that in the transition, you can use the type like this:
__timezone Europe/Berlin
__timezone --timezone Europe/Berlin
With the first call, it's map the "object id" to the…
This would require cdist core code changes, only for this one type. What is deprecated here then? Object id? Or better, type nature?
Since no one could really come up with a good solution to the transition issue, do you think we can go forward with !916 and add a "breaking changes" section to the…
@ander Right, the variable name is wrong, it is __target_hostname. I will just remove those warnings. They don't have any special usage meaning anyway.
@ssrq Is the above change: first I used hosts type without alias, run cdist config; then I changed usage of hosts type so that I added alias and run cdist config? If yes, then this cannot be done…
@ssrq Also take a look at the following discussion: https://code.ungleich.ch/ungleich-public/cdist/-/merge_requests/465. I think that Dmitry purposely didn't support alias, multiple names are managed…
changed title from __hosts: {---alias -}modification results in duplicate lines to __hosts: modification results in duplicate lines