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

Sorry, we were unable to convert your code. #105

Closed
rkochar opened this issue Oct 17, 2023 · 2 comments
Closed

Sorry, we were unable to convert your code. #105

rkochar opened this issue Oct 17, 2023 · 2 comments
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@rkochar
Copy link

rkochar commented Oct 17, 2023

What happened?

I am trying out Pulumi and wanted to convert some simple kubernetes yaml files. They fail with "Sorry, we were unable to convert your code." and further down "could not read output file: : open : no such file or directory" on the browser at https://www.pulumi.com/kube2pulumi/.

Example

This is fairly simple code. I put this into the Custom tab and clicked "Convert".

apiVersion: v1
kind: Namespace
metadata:
  name: "kafka"
  labels:
    name: "kafka"

Output of pulumi about

https://www.pulumi.com/kube2pulumi/

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).

@rkochar rkochar added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Oct 17, 2023
@mikhailshilkov
Copy link
Member

I can reproduce your error... Interestingly, the following code works

apiVersion: v1
kind: Namespace
metadata:
  name: "kafka"
  labels:
    name: kafka

(the only difference is quotes around the label name)

We'll need to check what is going on.

@mikhailshilkov mikhailshilkov removed the needs-triage Needs attention from the triage team label Oct 21, 2023
@rquitales
Copy link
Member

This issue no longer reproduces. Likely fixed by: #110

@rquitales rquitales self-assigned this Feb 2, 2024
@rquitales rquitales added the resolution/fixed This issue was fixed label Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

3 participants