This message was deleted.

sparse-intern-71089

11/20/2020, 3:12 PM

This message was deleted.

✔️ 1

adamant-translator-31969

11/20/2020, 3:13 PM

When I try to import daemonset only with import:id , pulumi ask me all attributes to do import

adamant-translator-31969

11/20/2020, 3:32 PM

I'm programming with TS in AWS environment

billowy-army-68599

11/20/2020, 8:59 PM

once you import a resource into a pulumi program, you need to flesh out the code to match the current running state

adamant-translator-31969

11/21/2020, 10:40 PM

@billowy-army-68599 yes, in my stage: fist I run a k8s.apps.Daemonset.get() method to get information about existing daemonSet ...after this I try to run this code

adamant-translator-31969

11/21/2020, 10:41 PM

const kubeProxy = new k8s.apps.v1.DaemonSet(

'kube-proxy',

metadata: metadaObtained (this variable is obtained from k8s.DaemonSet.get method),

spec: specObtained (this variable is obtained from k8s.apps.DaemonSet.get method)

},

updateStrategy: spec.updateStrategy,

},

},

provider: providerK8s,

import: 'kube-system/kube-proxy',

adamant-translator-31969

11/21/2020, 10:45 PM

But, Import in pulumi failed because pulumi ask me more info, for instance: in VolumeMounts, Volumes, containers. When I print data (spec, annotation) obtained from K8S.apps.daemonset.get method this output

6 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.