Skip to content
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.

Compose: don't export null values #636

Merged
merged 1 commit into from
Jun 18, 2015

Conversation

alena1108
Copy link
Contributor

  1. Don't include null values to docker/rancher-compose.yml
  2. Remove requestedHostId/cpuSet from rancher-compose (used to keep there
    as docker-compose doesn't support these params, but never read them). We can re-enable cpuSet, but to put it to the docker-compose.yml once docker-compose starts supporting it (docker-compose.yml should support every docker run option docker/compose#754)

Remove requestedHostId/cpuSet from rancher-compose (used to keep there
as docker-compose doesn't support these params, but never read them). We
can re-enable cpuSet, but to put it to the docker-compose.yml once
docker-compose starts support it
@sonchang
Copy link
Contributor

LGTM. Wondering whether we should do a StringUtils.isEmpty() check or is null sufficient

@alena1108
Copy link
Contributor Author

@sonchang I'll keep it in mind as a future improvement.

ibuildthecloud added a commit that referenced this pull request Jun 18, 2015
Compose: don't export null values
@ibuildthecloud ibuildthecloud merged commit 753f13a into rancher:master Jun 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants