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.

Sign up for GitHub

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

Jump to bottom

Using I/O to form the file path of the CNI YAML creates errors in the dynamic provider since it can't locate the file #219

Closed
metral opened this issue Aug 12, 2019 · 0 comments · Fixed by #223
Closed

Using I/O to form the file path of the CNI YAML creates errors in the dynamic provider since it can't locate the file #219

metral opened this issue Aug 12, 2019 · 0 comments · Fixed by #223
Assignees
@metral
Labels
kind/bug Some behavior is incorrect or out of spec kind/enhancement Improvements or new features
Milestone
0.26

Comments

@metral
Copy link
Contributor

metral commented Aug 12, 2019 •
edited
Loading

A user hit this error per a recent PR change that attempted to fix how the file path of the CNI YAML file is computed.

Diagnostics:
  pulumi-nodejs:dynamic:Resource (arcus-alpha-aws-vpc-cni):
    error: Plan apply failed: ENOENT: no such file or directory, open '/PROJECT_PATH/src/node_modules/@pulumi/eks/cni/aws-k8s-cni.yaml'

A temporary work around seems to be to export the state, manually edit the CNI file path stored in the dynamic provider to the correct path, and then re-import the state.

Related: #149.

We should consider ingesting the CNI YAML content and then passing this value to the dynamic provider, rather than trying to form the file's relative path on the client and read it through I/O.
@metral metral added the bug label Aug 12, 2019
@metral metral self-assigned this Aug 12, 2019
@metral metral changed the title Using I/O to form the file path of the CNI YAML is leading to errors in the dynamic provider not being able to locate the file: Plan apply failed: ENOENT: no such file or directory Using I/O to form the file path of the CNI YAML is leading to errors in the dynamic provider not being able to locate the file Aug 12, 2019
@metral metral added this to the 0.26 milestone Aug 12, 2019
@metral metral changed the title Using I/O to form the file path of the CNI YAML is leading to errors in the dynamic provider not being able to locate the file Using I/O to form the file path of the CNI YAML creates errors in the dynamic provider since it can't locate the file Aug 12, 2019
@metral metral mentioned this issue Aug 13, 2019
Merged
@infin8x infin8x added kind/enhancement Improvements or new features kind/bug Some behavior is incorrect or out of spec labels Jul 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@metral metral

Labels
kind/bug Some behavior is incorrect or out of spec kind/enhancement Improvements or new features
Projects
None yet
Milestone
0.26
Development

Successfully merging a pull request may close this issue.

fix(cni): read CNI YAML outside of the dynamic provider and update to v1.5.3 pulumi/pulumi-eks
3 participants
@lukehoban @infin8x @metral