Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bugfix for https://github.com/google/caliban/issues/65 #67

Merged
merged 1 commit into from
Aug 2, 2020

Conversation

ajslone
Copy link
Collaborator

@ajslone ajslone commented Aug 2, 2020

This addresses an error where we specify resource maxima for GKE clusters using quota information returned from the GCP compute API. The API can return a quota of zero for a given resource type, but requesting a limit of zero in the cluster creation API causes an error, so this change prevents setting a limit of zero for any resource.

@codecov
Copy link

codecov bot commented Aug 2, 2020

Codecov Report

Merging #67 into master will increase coverage by 0.26%.
The diff coverage is 66.66%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
+ Coverage   51.41%   51.68%   +0.26%     
==========================================
  Files          30       30              
  Lines        2970     2972       +2     
==========================================
+ Hits         1527     1536       +9     
+ Misses       1443     1436       -7     
Impacted Files Coverage Δ
caliban/platform/gke/util.py 72.90% <66.66%> (+2.51%) ⬆️
caliban/util/fs.py 89.62% <0.00%> (-0.95%) ⬇️
caliban/util/auth.py 76.19% <0.00%> (+9.52%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af9dd99...1b5e274. Read the comment docs.

@ajslone ajslone merged commit 7c75f38 into master Aug 2, 2020
@ajslone ajslone deleted the aslone/gke_resource_limit_fix branch August 2, 2020 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant