-
Notifications
You must be signed in to change notification settings - Fork 17
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
crontabs default example not working on python "pkg_resources.DistributionNotFound" #106
Comments
Hey @notdodo, thanks for the bug report. We're currently determining how to integrate crd2pulumi into our other migration tools. I expect crd2pulumi to be in maintenance mode until we've decided how to do that. Could you tell me a little more about your use case for crd2pulumi? In the mean time we'll keep this issue open as it's a valid bug report. |
Hi @AaronFriel, the use case is simply to use it to have pulumi CRDs for ECK (https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-eck.html) instead of manually writing pulumi resources or using yaml files. |
That makes sense, thanks. |
@AaronFriel Hi any update on this please? I'm seeing the same issue, the use case is the same, integrating CRD in the pulumi code using python. |
I'm also running into this issue with python and crd2pulumi |
Added to epic https://github.com/pulumi/home/issues/3431 |
What happened?
Following the python example to create CRDs inside pulumi during the pulumi up command the following error is returned:
Changing the import from
import crontabs.pulumi_crds as crontabs
toimport crontabs as crontabs
solve the pkg_resources error but the usage of the module is impacted.the error returned is now:
Expected Behavior
import of the module works and it's usable to create CRDs from python
Steps to reproduce
1- download the yaml for the CRDs for crontabs from the example
2- crd2pulumi --pythonPath ./crontabs customresources.yaml
3- use the module
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: