Andy Roth
Different idea: if the `# @schema` comment is on a different line, require a field that ties it back to the yaml key that you want it associated with. This...
Given the latest change with `-schemaRoot.id`, `-schemaRoot.title`, and `schemaRoot.description` flags, it makes sense to add a `-schemaRoot.additionalProperties` flag.
Something else I discovered is that on my Macbook the error didn't happen. There's something different with how `docker run` behaves between Mac and Linux when it comes to mounting...
The first place it happened for me was in a GitHub Actions run, then confirmed on my local Rocky9 box after about 2 hours of troubleshooting 🙃
Recommend we break this down more into some specific use cases that have been identified as difficult without some of the capabilities that zarf brings to the table, as well...
The persona I have described is not the person who is developing/creating the package, so I would not be able to change what the defaults are as they are defined...
If we, for example, publish DUBBD as a reusable/downloadable package, I'm gonna have things that I need to set that are specific to my use case, but can be the...
If we were to have the same configuration value in multiple configuration files, and they all need to stay in lockstep, there is a high chance that mistakes will be...
No I'm suggesting exactly what you are saying as well.
Except that in my use case the variable `c` would not be present in `base-values.yaml` since its value always must be different in each environment. I would have * `values.yaml`...