Replies: 4 comments
-
I'm not opossed to it, most if not all use cases of looping over environments can be covered by |
Beta Was this translation helpful? Give feedback.
-
Only suggestion I can come up with: Maybe if we just replace |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Beta Was this translation helpful? Give feedback.
-
That doesn't seem related @James-Riordan, please move this to the discussions tab. |
Beta Was this translation helpful? Give feedback.
-
Regular (static and single-inline) environments are specified like so:
Given
environments/default/main.jsonnet
returns multipletanka.dev/Environment
objects, the following is required:While this usually works fine, it makes some automation much harder than needed. Previously this was possible:
This would have given you a diff of all environments. But it is impossible / unnecessarily hard to handle the flag case because we only know once it failed.
A solution to that would be to incorporate the name into the existing argument, maybe like so:
In return we could allow
tk env list
to return such strings, so above automation works again.I propose to add that as an alternative way solely handled in the
cmd/tk
package for now. Given the feature is experimental anyawys, we can iterate on this further.//cc @Duologic wdyt?
Beta Was this translation helpful? Give feedback.
All reactions