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

Error when parsing yaml file #985

Closed
krewi1 opened this issue Feb 10, 2020 · 3 comments
Closed

Error when parsing yaml file #985

krewi1 opened this issue Feb 10, 2020 · 3 comments
Assignees
Labels
p1 A bug severe enough to be the next item assigned to an engineer
Milestone

Comments

@krewi1
Copy link

krewi1 commented Feb 10, 2020

Problem description

There is error when parsing yaml file with k8s.yaml.ConfigFile. The example yaml is:

apiVersion: v1
kind: ServiceAccount
metadata:
  name: azurerunner-operator

Whole load yaml stuff looks like this

export const serviceAccount = new k8s.yaml.ConfigFile("serviceAccount", {
    file: `${__dirname}/backend/service_account.yaml`
}, {
    parent: aks
});

Errors & Logs

error: Running program '/current' failed with an unhandled exception:
TypeError: Cannot read property 'map' of undefined
at config.objs.then.configObjs (/current/node_modules/@pulumi/kubernetes/yaml/yaml.js:182:14)

Affected product version(s)

v1.10.1

Reproducing the issue

Sorry, not possible

@krewi1
Copy link
Author

krewi1 commented Feb 11, 2020

The error happends when we specify parent property for ComponentResourceOptions

@lukehoban lukehoban added this to the 0.32 milestone Feb 11, 2020
@lukehoban
Copy link
Member

I believe a fix for this is being worked on in #987.

@lblackstone
Copy link
Member

This should be fixed in v1.5.3, which includes #987

@infin8x infin8x added the p1 A bug severe enough to be the next item assigned to an engineer label Jul 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p1 A bug severe enough to be the next item assigned to an engineer
Projects
None yet
Development

No branches or pull requests

4 participants