Open
Description
Describe the bug
Currently, while deploying the resources, e.g. big query table, if any resource failed to deploy because of any reason, then in next run the resource gets ignored.
To Reproduce
Steps to reproduce the behavior:
- create a big query table as a resource in dwh repository
- do not register or delete the secrets TASK_BQ2BQ and DATASTORE_BIGQUERY and STORAGE secret
- run optimus deploy to deploy the resources
- here the deploy command will fail, with error that secrets are not configured.
- register TASK_BQ2BQ and DATASTORE_BIGQUERY and STORAGE with appropriate service account.
- run the deploy command again.
- the table will be ignored with message
{table_name} is skipped because incoming resource is the same as existing resources
Expected behavior
Table which were unable to sync to big query should be part of optimus deploy