Config Imports Should be default pass through the current profile(s) #5707
Labels
area/config
feature/multi-configs
kind/feature-request
planning/Q2-21
priority/p2
May take a couple of releases
source/partnerships
Milestone
By default Importing a config (I think) is just running the default profile unless otherwise specified. We have multiple nestings of skaffold.yaml configs (for microservices and groups of microservices) and were expecting that profiles were inherited on the way down.
We would much prefer and expect that skaffold applies the current profile(s) unless otherwise specified.
Our root skaffold.yaml has gotten pretty messy, and is 50% profile activation code. We ultimately fixed with yaml anchors. But when we add a profile, we basically have to track down every single 'requires' section in all our skaffold yamls (not just root) to make sure we add the appropriate profiles.
This would be breaking change for anyone importing a config and just using the default profile (not many use cases for this I'm thinking?)
The text was updated successfully, but these errors were encountered: