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

Add labels to OpenFaas functions from the function spec #40

Closed
utsavanand2 opened this issue Feb 5, 2020 · 5 comments · Fixed by #45
Closed

Add labels to OpenFaas functions from the function spec #40

utsavanand2 opened this issue Feb 5, 2020 · 5 comments · Fixed by #45
Assignees

Comments

@utsavanand2
Copy link
Contributor

Add labels to OpenFaas functions from the function spec

Expected Behaviour

We should be able to add a label to a function by adding it to container definition.

So, when we run:
faas-cli store deploy figlet --label hello=world

We should get back the labels with:
faas-cli describe figlet

Current Behaviour

Labels are not added

Possible Solution

A PR is in the works

Steps to Reproduce (for bugs)

1>faas-cli store deploy figlet --label hello=world
2> faas-cli describe figlet # Won't print out labels

This feature works perfectly with faas-netes (OpenFaas running on Kubernetes), but we need to port this functionality here too.

This issue is a duplicate of this issue by @alexellis on the archived faas-containerd repo

@martindekov
Copy link
Contributor

I can take a look at this 👍

@martindekov
Copy link
Contributor

Derek assign: me

@alexellis
Copy link
Member

Thank you 💪

@carlosedp
Copy link
Contributor

Hey @martindekov, I've added some references on the previous issue:

Doc: https://godoc.org/github.com/containerd/containerd#WithContainerLabels

Code:

container, err := client.NewContainer(
.

@martindekov
Copy link
Contributor

Thanks for pointing the right place @carlosedp 👍 Definitely saved me time searching it 🍻

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 a pull request may close this issue.

4 participants