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

Filtering mechanisms for incus_image datasource #187

Open
jonatas-lima opened this issue Dec 16, 2024 · 0 comments
Open

Filtering mechanisms for incus_image datasource #187

jonatas-lima opened this issue Dec 16, 2024 · 0 comments

Comments

@jonatas-lima
Copy link
Contributor

Some cloud image datasources provide filtering mechanisms, such as the most_recent and name_regex parameters in aws_ami or google_compute_instance. I reviewed the code and identified two possible approaches to implement this feature:

  1. Client-side approach: Query all image aliases to Incus server, then apply the filters within the provider.

or

  1. Server-side approach: Modify the Incus server image_alias to accept filtering parameters directly. Something like here.

Which approach do you think would be more appropriate?

If this issue seems relevant, I’d be happy to contribute by working on it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant