-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename cloud_type from GCE to GCP, clarify throughout #58
Conversation
Theoretically, application playbooks should not have a dependency upon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - confirmed not being a breaking change.
Contrary to my earlier statement, the change will require all application playbooks that use clusterverse with GCP to change the |
Maybe there are few enough users within GCP that this has a fairly small impact right now? |
It was my thought as well as this is, by all means, a cosmetic change. However, with a wider GCP adoption in the future this might get flagged nonetheless. The expected changes from Clusterverse/GCP user point-of-view is a one-liner:
... so I doubt it will create much backlash. What are your thoughts @mikekrasn and @flfernandez ? |
The change is indeed minimal from a user perspective. I personally agree with it. |
Currently for Persistence there is no worries changing this, but I know that Content Discovery used clusterverse for their Couchbase build out in GCP towards the end of last year. I think we'd need to sync with them on this change, but as Patrik's said it's a small modification of the cloud type value so I don't think it would be an issue |
@sky-amoncadot : I don't know who picked up the Couchbase work in CD, as KL has left the department, but from your perspective would this be a major impacting change? |
Confirmed by @PreeyanP this isn't an issue for CD |
cloud_type
was renamed fromgce
togcp
to maintain consistency with the aws/ec2 documentation and usage throughout the playbook.It introduces one breaking change for playbooks that run on GCP, as the
cloud_type
variable would have to be renamed.