You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
---
region: us-east-1
_instance_tags_to_propagate:
- 'Environment'
_volume_tags_to_propagate:
- 'Environment'
_volume_tags_to_be_set:
# - key: 'role'
# value: 'ebs'
_snapshot_tags_to_be_set:
# - key: 'role'
# value: 'ebs_snapshot'
_instance_filter:
# Filter values with the same key (eg, tag:app) are an OR
# Different filter keys are an AND operation (eg, tag:app and tag:team)
# See the Filter section in http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInstances.html#API_DescribeInstances_RequestParameters
# Example entries:
# 'tag:app': ['app1', 'app2']
# 'tag:team': 'team1'
_volumes_to_tag:
# An empty list means tag all volumes
# Example entries:
# - 'vol-1ab2c345'
- 'vol-0784cc294e20cbb39'
_snapshots_to_tag:
# An empty list means tag all snapshots
# Example entries:
# - 'snap-12ab3c45'
# - 'snap-6de7f890'
Running ./graffiti-monkey --config ../conf/example_config.yml --append --nosnapshots --dryrun tells me it is going to make the following changes, adding the Environment tag:
2018-06-13 20:24:08 [INFO] Starting Graffiti Monkey
2018-06-13 20:24:08 [INFO] Options: dryrun True, append True, novolumes False, nosnapshots True
2018-06-13 20:24:08 [INFO] Connecting to region us-east-1 using profile default
2018-06-13 20:24:08 [INFO] Using volume list from cli/config file
2018-06-13 20:24:09 [INFO] Found 1 volume(s)
2018-06-13 20:24:09 [INFO] Processing volume 1 of 1 total volumes
2018-06-13 20:24:09 [INFO] DRYRUN: Volume vol-0784cc294e20cbb39 would have been tagged {u'Name': u'kubernetes.metismachine.io-dynamic-pvc-46cc64b6-6a94-11e8-a763-02c1f252ba9e', u'kubernetes.io/created-for/pvc/namespace': u'spark-cluster', u'kubernetes.io/cluster/kubernetes.metismachine.io': u'owned', u'kubernetes.io/created-for/pvc/name': u'cassandra-data-cassandra-3', 'Environment': u'production', u'kubernetes.io/created-for/pv/name': u'pvc-46cc64b6-6a94-11e8-a763-02c1f252ba9e', u'KubernetesCluster': u'kubernetes.metismachine.io'}
2018-06-13 20:24:09 [INFO] Processed a total of 300 GB of AWS Volumes
2018-06-13 20:24:09 [INFO] Completed processing all volumes
2018-06-13 20:24:09 [INFO] Graffiti Monkey completed successfully!
However, when I run it without the --dryrun, it tells me it ran successfully but the EBS volume, the one in my config file, vol-0784cc294e20cbb39, the one in my AWS account, does not have the new Environment tag.
[20:24] jmorganwalker@ip-10-0-1-11:~DEV_ROOT/graffiti-monkey/bin# ./graffiti-monkey --config ../conf/example_config.yml --append --nosnapshots master ✱ ◼
2018-06-13 20:24:29 [INFO] Starting Graffiti Monkey
2018-06-13 20:24:29 [INFO] Options: dryrun False, append True, novolumes False, nosnapshots True
2018-06-13 20:24:29 [INFO] Connecting to region us-east-1 using profile default
2018-06-13 20:24:29 [INFO] Using volume list from cli/config file
2018-06-13 20:24:30 [INFO] Found 1 volume(s)
2018-06-13 20:24:30 [INFO] Processing volume 1 of 1 total volumes
2018-06-13 20:24:30 [INFO] Processed a total of 300 GB of AWS Volumes
2018-06-13 20:24:30 [INFO] Completed processing all volumes
2018-06-13 20:24:30 [INFO] Graffiti Monkey completed successfully!
I tried running with -vvvvv and I can see it go through what seems to be a successful boto responses but still nothing in AWS
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I've made the following changes:
core.py
:./graffiti-monkey --config ../conf/example_config.yml --append --nosnapshots --dryrun
tells me it is going to make the following changes, adding theEnvironment
tag:--dryrun
, it tells me it ran successfully but the EBS volume, the one in my config file,vol-0784cc294e20cbb39
, the one in my AWS account, does not have the newEnvironment
tag.-vvvvv
and I can see it go through what seems to be a successful boto responses but still nothing in AWSAny help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: