Webb Brown

@AjayTripathy and @teevans already did this to create the OpenCost repo. This will be similar but just moving to github.com/opencost org. Plan is to do this after 1.95 release.

+1, what API(s) do you feel are highest priority?

If we add _sort_ request field then this should be straightforward? If so, requests params of `pageSize`,`pageNum`,`sortField` seem reasonable to me. We'll then want to return metadata about page, totalResults,...

@pierluigilenoci any more details you can share on what would be helpful? Most teams have requested doing this via YAML, would love to hear what would be helpful for you.

We currently have an API for this, but it's undergoing some changes as move from the `checks` jobs to our core Go application. We can share documentation once it's ready...

@pierluigilenoci there are two relevant APIs here. Would be interested in your general feedback/questions and then we can look to document these APIs more completely! `/api/setNamespaceAttributes` -- used to set...

Here's an example output: ``` {"byNamespace": { "data-science":{"value":"20","alert":"true","namespace":"data-science"}, "frontend-services":{"value":"500","alert":"false","namespace":"frontend-services"} } } ``` Did you accidentally set a value for empty namespace? I'm not able to recreate that or the behavior...

Thanks for the report, @SapientGuardian! @mbolt35 would love to get your input here while I review this week. One thing to point out is that AWS cost reconciliation would account...

@munjalpatel today, this feature does not consider usageType, e.g. spot vs on-demand. It provides a recommendation on the amount of resources required.

This is actually being built separately but will likely be integrated in the future! No set timeline at this point.