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
Is your feature request related to a problem? Please describe.
When planning a deployment with multiple namespaces you don't see which namespaces spacegun is currently in. If I have deployments with the same name in 2 different namespaces, I can't tell which will be applied when I don't filter one or the other out.
Describe the solution you'd like
Add the namespace to the plan logs. For example: planning in namespace first: planning image deployment my-importer in importers planning image deployment other-importer in importers planning in namespace second: planning image deployment my-importer in importers-live
Same for the planned deployment log: namespace1: my-importer ... => ... namespace2: other-importer ... => ...
Describe alternatives you've considered
You could also incorporate the importer in the same line like: planning image deployment my-importer in namespace first in importers other-importer namespace1 ... => ...
but that seems a bit cluttered.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When planning a deployment with multiple namespaces you don't see which namespaces spacegun is currently in. If I have deployments with the same name in 2 different namespaces, I can't tell which will be applied when I don't filter one or the other out.
Describe the solution you'd like
Add the namespace to the plan logs. For example:
planning in namespace first:
planning image deployment my-importer in importers
planning image deployment other-importer in importers
planning in namespace second:
planning image deployment my-importer in importers-live
Same for the planned deployment log:
namespace1:
my-importer ... => ...
namespace2:
other-importer ... => ...
Describe alternatives you've considered
You could also incorporate the importer in the same line like:
planning image deployment my-importer in namespace first in importers
other-importer namespace1 ... => ...
but that seems a bit cluttered.
The text was updated successfully, but these errors were encountered: