Destroy playbook does not detect/destroy vpc

[gmontalvoy]

Hi there,

Testing the examples provided by the own repository, I realize the destroy.yaml playbook does not detect and ,eventually destroy, the resources created by the create.yaml playbook.

TASK [Gathering Facts] ******************************************************************************************************************************************************************
ok: [localhost]

TASK [Release Floating IP] **************************************************************************************************************************************************************
skipping: [localhost] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Remove VSI] ***********************************************************************************************************************************************************************
skipping: [localhost] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Remove SSH Key] *******************************************************************************************************************************************************************
skipping: [localhost] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Remove VPC Subnet] ****************************************************************************************************************************************************************
skipping: [localhost] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Remove VPC] ***********************************************************************************************************************************************************************
skipping: [localhost] => {"changed": false, "skip_reason": "Conditional result was False"}

PLAY RECAP ******************************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=0    skipped=5    rescued=0    ignored=0   

The resources are still on the ibm cloud

[Anil-CM]

Have updated the example to address this issue. Please have look https://github.com/IBM-Cloud/ansible-collection-ibm/tree/master/examples/simple-vm-ssh