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
{{ message }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
I noticed that landscaper supports the --namespace option for setting the namespace a helm chart is deployed to. To be clear - this is not what I'm after....
I would like landscaper to be able to do diffs based on a namespace.
and only changes to deployment3-4 would be applied
My use case is I have multiple teams, each working in different namespaces. With landscaper currently, a mistake by one team can block deployments in another team. Applying by namespace would solve this.
thanks
James M
The text was updated successfully, but these errors were encountered:
How are you organising your landscape component files? We had a similar challenge with multiple namespaces in our repository, so now we use a directory per namespace. Then our release manager landscapes each namespace independently when changes are made to that directory.
I noticed that landscaper supports the
--namespace
option for setting the namespace a helm chart is deployed to. To be clear - this is not what I'm after....I would like landscaper to be able to do diffs based on a namespace.
eg.
currently, if landscaper knows about deployments1-4, there's no way to only consider/diff/apply changes to a particular namespace only.
eg.
I change all of the deployments, but I only want to consider "namespace-bar" changes for landscaping right now.
I could then do
landscaper apply --only-namespace namespace-bar *.yaml
and only changes to deployment3-4 would be applied
My use case is I have multiple teams, each working in different namespaces. With landscaper currently, a mistake by one team can block deployments in another team. Applying by namespace would solve this.
thanks
James M
The text was updated successfully, but these errors were encountered: