https://pulumi.com logo
#general
Title
# general
m

millions-judge-24978

11/25/2019, 6:41 PM
I’d like to try out the
pulumi up --target
option, however I am seeing that the preview is not limited to the targeted URN I provide. Is that expected? Will the targeting only affect the actual
up
once I approve it.
w

white-balloon-205

11/25/2019, 6:49 PM
Could you share the output you are seeing by any chance? Note that there were a couple improvements here in the 1.6.0 release last week: https://github.com/pulumi/pulumi/issues/2522
m

millions-judge-24978

11/25/2019, 6:50 PM
I did actually upgrade to
1.6.0
already. This is what I’m seeing currently:
Copy code
❯ pulumi up --suppress-outputs -t urn:pulumi:clusters::infrastructure::spotinst:aws/ocean:Ocean::web-dev --target-dependents
Previewing update (clusters):

     Type                   Name                     Plan       Info
     pulumi:pulumi:Stack    infrastructure-clusters             
 =   ├─ spotinst:aws:Ocean  cluster-us2              import     [diff: -userData,whitelists~imageId,tags]; 1 warning
 =   ├─ spotinst:aws:Ocean  cluster-us1              import     [diff: -userData~imageId,rootVolumeSize,tags]; 1 warning
 +   └─ spotinst:aws:Ocean  web-dev                  create     
 
Diagnostics:
  spotinst:aws:Ocean (cluster-us2):
    warning: inputs to import do not match the existing resource; importing this resource will fail
 
  spotinst:aws:Ocean (cluster-us1):
    warning: inputs to import do not match the existing resource; importing this resource will fail
 
Resources:
    + 1 to create
    = 2 to import
    3 changes. 239 unchanged

Do you want to perform this update? no
confirmation declined, not proceeding with the update
I have tried it in the past with less weird conditions (no imports) and saw the same behavior
3 Views