I'm doing some sort of post-processing on the generated YAML to be able to omit BuildConfig (as mentioned in #446) etc. When I'm done, I save it to a versioned file to be able to keep track of production config.
When running kompose convert --provider openshift --verbose --stdout (which produces a kind: list), services' and configuration blocks' order seems to be generated arbitrarily. As this is unimportant for general usage, you might provide a nice UX boost just by sorting the output which would make having it be stable and diffs actually meaningful.
For example, you might go with:
- serviceA,
BuildConfig
- serviceA,
DeploymentConfig
- serviceB,
BuildConfig
- serviceB,
DeploymentConfig
- etc.
Also, stuff like environment variables and service ports might get sorted by name.
I'm doing some sort of post-processing on the generated YAML to be able to omit
BuildConfig(as mentioned in #446) etc. When I'm done, I save it to a versioned file to be able to keep track of production config.When running
kompose convert --provider openshift --verbose --stdout(which produces akind: list), services' and configuration blocks' order seems to be generated arbitrarily. As this is unimportant for general usage, you might provide a nice UX boost just by sorting the output which would make having it be stable and diffs actually meaningful.For example, you might go with:
BuildConfigDeploymentConfigBuildConfigDeploymentConfigAlso, stuff like environment variables and service ports might get sorted by
name.