Skip to content

Conversation

chrised
Copy link

@chrised chrised commented Feb 1, 2018

And only include them in the output if they actually exist

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 99.956% when pulling 61c1416 on chrised:collection_cluster_properties into 99a7269 on joowani:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 99.956% when pulling 61c1416 on chrised:collection_cluster_properties into 99a7269 on joowani:master.

@coveralls
Copy link

coveralls commented Feb 1, 2018

Coverage Status

Coverage decreased (-0.04%) to 99.956% when pulling 88421dc on chrised:collection_cluster_properties into 99a7269 on joowani:master.

@chrised chrised changed the title Add cluster-only properties for collections WIP: Add cluster-only properties for collections Feb 1, 2018
@chrised
Copy link
Author

chrised commented Feb 1, 2018

4d163bf appears to work from my local testing against both an unclustered and clustered instance, but it looks like coverage is dropped if I run this against an unclustered deployment, and many things appear to go horribly wrong when I try and run the test suite against a clustered deployment.

And only include them in the output if they actually exist
Also use bash on TravisCI
@joowani
Copy link
Contributor

joowani commented May 16, 2018

This feature is already implemented in the latest version.

@joowani joowani closed this May 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants