You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
using the cue api I want to process some custom attributes in cue source files. This requires the path to the file where the attribute was found. The attached testscript.txtar shows a minimal example to reproduce the issue. This works for cm1, but fails for cm2. Instead of the expected path, the path to the k8s definition is returned. Is this behavior expected? The restult is the same for v0.4.3 and v0.5.0-beta.2.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
using the cue api I want to process some custom attributes in cue source files. This requires the path to the file where the attribute was found. The attached
testscript.txtar
shows a minimal example to reproduce the issue. This works forcm1
, but fails forcm2
. Instead of the expected path, the path to the k8s definition is returned. Is this behavior expected? The restult is the same for v0.4.3 and v0.5.0-beta.2.testscript output:
Putting some dummy value into
cm2.data
results in the expected path to be returned.
testscript.txtar
Beta Was this translation helpful? Give feedback.
All reactions