Multiple Dry Runs Show Same resources

[altoic]

So testing a basic vpc check for an email tag

policies:
  - name: VPCTags
    resource: vpc
    filters:
      - "tag:Default": absent
    actions:
      - type: mark
        key: CloudCustodianIdentified
        value: Missing email tag

I run

custodian run --dryrun -s . vpctag.yml
2017-05-23 14:45:35,308 - custodian.policy - INFO - policy: VPCTags resource:vpc region:us-east-2 count:4 time:0.00

Then tried to add that 'Default' tag on 2 VPCs hoping something would take effect

custodian run --dryrun -s . vpctag.yml
2017-05-23 14:47:49,008 - custodian.policy - INFO - policy: VPCTags resource:vpc region:us-east-2 count:4 time:0.00

The same amount of VPCs will have actionable items. Looks like it is caching API calls? Maybe?
Is this not the proper method of performing dry runs?

[tim-elliott]

Yes, there is caching of results. You can avoid that by using the --cache-period option with a value of 0, i.e.
custodian run --dryrun --cache-period 0 -s . vpctag.yml

[altoic]

thanks @tim-elliott problem solved.

BTW how are people finding these unique values to set? I feel like to get very familiar with this I would have to just dive straight into the source.

[tim-elliott]

The -h option is available with most if not all custodian commands. So custodian run -h will give you the valid options for the run command, with brief explanations, including

  --cache-period CACHE_PERIOD
                        Cache validity in minutes (default 15)

[altoic]

thanks. just had to go one step deeper...