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

Filter kraft cloud images by namespace #1331

Open
nderjung opened this issue Mar 1, 2024 · 2 comments
Open

Filter kraft cloud images by namespace #1331

nderjung opened this issue Mar 1, 2024 · 2 comments
Labels
kind/enhancement New feature or request priority/low Nice to have issues thatare not urgent, but can be nagging.

Comments

@nderjung
Copy link
Member

nderjung commented Mar 1, 2024

Feature request summary

This ticket tracks adding the ability to filter images retrieved by kraft cloud image ls by namespace. This can be done by introducing a new flag, --namespace.

Describe alternatives

No response

Related architectures

None

Related platforms

None

Additional context

No response

@nderjung nderjung added the kind/enhancement New feature or request label Mar 1, 2024
@antoineco
Copy link
Contributor

This needs refinement. The important part is not about adding a flag here, but what users should expect to be able to do and how.

For instance:

  • Can a user request images from multiple namespaces at a time? (note that I am not asking about technicals, such as whether the flag can be passed multiple times or if it should accept comma delimited values)
  • Can a KraftCloud user even list anything besides their own namespace and "official"?
  • Should the namespace reflect the user name, or friendly aliases such as "owner" vs. "official"? This is important because, when we hand over tokens, the user name that they were assigned is not explicit to the user.

@marcrittinghaus
Copy link
Member

  • I don't think this is a requirement. We can add a comma separated list if this is requested by users
  • Not the regular user in the default config. But it is just a matter of setting additional permissions. For example, this is the case with some internal accounts like test
  • We always give the username and the token. I would also keep this and not hide it by owner. We can configure users to have access to multiple projects.

@craciunoiuc craciunoiuc added the priority/low Nice to have issues thatare not urgent, but can be nagging. label Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request priority/low Nice to have issues thatare not urgent, but can be nagging.
Projects
None yet
Development

No branches or pull requests

4 participants