Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Feature Request: per-namespace apply #114

Open
james-masson opened this issue Feb 23, 2018 · 4 comments
Open

Feature Request: per-namespace apply #114

james-masson opened this issue Feb 23, 2018 · 4 comments

Comments

@james-masson
Copy link

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.

namespace-foo>
                             deployment1.yaml
                             deployment2.yaml
namespace-bar>
                             deployment3.yaml
                             deployment4.yaml

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

@johnhofman
Copy link
Contributor

Hi James,

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.

Cheers,
John.

@james-masson
Copy link
Author

I do have a directory per namespace. However, landscaper tries to remove all deployments not in that directory/namespace if I only apply on a subset.

@royjs
Copy link
Contributor

royjs commented Feb 28, 2018

You can use the --disable=delete flag. This will prevent deleting what is not in your subset.

@james-masson
Copy link
Author

Perhaps, but that's a manual workaround at best - not suitable for a CI process.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants