Open alex4poshmark opened 4 years ago
It appears issue is that Redshift cluster is not created in VPC so there is no VpcId associated. But it looks like VpcId is required in other places. Do you plan to address this or non-VPC Redshift should be skipped?
This should be fixed, but I won't have time to get to this until February, 2020.
Any chance of a work around in the meantime?
If you don't mind removing Redshift from the results, one workaround is to comment out the redshift code In commands/prepare.py:
# Redshift clusters #for node_json in get_redshift(region): # node = Redshift(region, node_json) # nodes[node.arn] = node
If you don't mind removing Redshift from the results, one workaround is to comment out the redshift code In commands/prepare.py:
Redshift clusters
for node_json in get_redshift(region):
node = Redshift(region, node_json)
nodes[node.arn] = node
Without the change to prepare.py - You get the following error: python cloudmapper.py report --account fws
With the change to prepare.py
#for node_json in get_redshift(region):
# node = Redshift(region, node_json)
# nodes[node.arn] = node
The error is: python cloudmapper.py prepare --account fws Building data for account fws (12...deleted to protect the innocent)
"collect" ran successfully but report fails:
python cloudmapper.py report --account myaccount