merging multiple instances of same package #3243
Unanswered
hansbogert
asked this question in
Q&A
Replies: 1 comment
-
|
sounds like this is a job for #3911 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a way to get a single instance after having done a
./...for a single package?Because we are in a transitioning from an intricate directory hierarchy with yamls (in the domain of Kubernetes), we'd like to have a single instance over the following directory hierarchy:
We
cue importall the yaml under a single package:That does mean all the package is shattered over multiple subdirectories:
However doing an eval shows us that we are dealing with multiple instances signalled byu the
// ---(if i understand correctly)In order to have policies which act on multiple applications we need to reference them in a cue file in
root/, however this seems problematic, take a simple toy policy inroot/:This results in the following:
Probably because
./...does a eval on./first . However, explicitly adding both subdirs does not work as well:I understand that you sometimes want to test instances of packages separately, i.e., a single directory and all its direct cue file therein belonging to a single package and
./...seems to do so by iterating over instances.However, sometimes it's really beneficial to be able to check all cue files recursively in a subdirectory and act on the config as if it is one instance. Is there a way to do that?
Of course I could do some bash-fuu and copy all cue files to the root dir, but that becomes pretty messy imo.
Beta Was this translation helpful? Give feedback.
All reactions