No, a refresh won't fix this issue, nor will destroy. I just want Pulumi to overwrite any resources in the way.
👍 1
limited-rain-96205
04/01/2021, 5:08 PM
For example, this is the error I'm seeing when trying to deploy, even with
-r
(refresh):
Copy code
01-Apr-2021 10:05:42 Retry #0; creation failed: <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "flannel" already exists
01-Apr-2021 10:05:42 error: resource flannel was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "flannel" already exists
l
loud-helicopter-75345
04/02/2021, 1:01 PM
I'm guessing the thinking is that when destroying unmanaged resources you would want to do this carefully and know exactly what Pulumi will destroy. However I can see your point if this is just a dev environment. Looking through the code I don't see any simple way to do this. Perhaps you could instead automate the step of removing these resources with whatever you used to create them?
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.