Remove unrestricted Cloudability view#8
Merged
Conversation
ciaramulligan
approved these changes
Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current code specifies a Cloudability "view" of
0, which means "unrestricted". We did this so that we could use explicit filtering to control the results, instead of imposing a Cost Center-centric view, which might exclude accounts which were incorrectly attributed. (At one point, interactively, we were using a view which included three cost centers.)However, the folks at Cloudability have tightened the controls, and we no longer have unrestricted access (and, trying to use it results in a
403/Forbiddenresponse). So, we either have to use the current user's default view (which seems prone to unreliable results), or we have to specify a particular view.This PR changes the code to specify the view for Cost Center 726.
In the course of creating this PR, the change was flagged by Dependabot as having security concerns. So, I've also updated to Go 1.24 and, in particular, updated the dependencies to include the current version of
golang.org/x/cryptowhich should address those.