Tanka: Our way of deploying to Kubernetes

Re:Tanka: Our way of deploying to Kubernetes by netfl0 on Friday January 10, 2020 @10:13AM (#22011466)

This article seems to have a major factual error. YAML does support “Repetition” with anchors. Am I missing something?

[ Parent | on HN ]

Re:Tanka: Our way of deploying to Kubernetes by shorez on Friday January 10, 2020 @10:18AM (#22011517)

Anchors are fairly limited:

- they are bound to a single file. This won’t help you when trying to maintain multiple similar sets of Config

- anchors do not support patching. If you need to change a nested key, you can’t do so without it affecting all other nested keys as well

[ Parent | on HN ]

Re:Tanka: Our way of deploying to Kubernetes by emptysea on Friday January 10, 2020 @10:30AM (#22011623)

Anchors also don't work with a list of elements.

For instance, if we want to share steps in a YAML based CI config we can't if they are a list.

[ Parent | on HN ]

Re:Tanka: Our way of deploying to Kubernetes by tyingq on Friday January 10, 2020 @10:22AM (#22011561)

I found that odd too. Typical examples like https://confluence.atlassian.com/bitbucket/yaml-anchors-9601... are pretty easy to map to their example of why they need repetition.

[ Parent | on HN ]