We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When users list or query functions from the REST API, then the memory limits set on the functions should be returned in the JSON response.
They are being accepted upon deployment, but not being populated when querying.
Try to read back from the task or container definition.
Update here:
https://github.com/openfaas/faasd/blob/master/pkg/provider/handlers/functions.go
https://github.com/openfaas/faasd/blob/master/pkg/provider/handlers/read.go
Required for terraform provider and API compliance.
The text was updated successfully, but these errors were encountered:
I would like to do that, if no one wants to 🙋🏻♂️
Sorry, something went wrong.
Given how long has passed since you volunteered to help, this issue is now fair game for anyone who wants to contribute.
Nobody is working on this at present.
/add label: help wanted, good first issue
@Shikachuu I don't think we have any CPU limits at this stage, so this just covers memory being populated back again from what was inputted.
See also: 9e5eb84
No branches or pull requests
Expected Behaviour
When users list or query functions from the REST API, then the memory limits set on the functions should be returned in the JSON response.
Current Behaviour
They are being accepted upon deployment, but not being populated when querying.
List all Possible Solutions
Try to read back from the task or container definition.
Update here:
https://github.com/openfaas/faasd/blob/master/pkg/provider/handlers/functions.go
https://github.com/openfaas/faasd/blob/master/pkg/provider/handlers/read.go
Context
Required for terraform provider and API compliance.
The text was updated successfully, but these errors were encountered: