-
Notifications
You must be signed in to change notification settings - Fork 52
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 variable name to cluster_domain #53
Comments
Oops, I don't know why it was clear in my mind when I wrote this 🤔 ... So, Thanks for your issue 😄. NOTE: However, we have to keep in mind that this will break compatibility (so we also have to keep |
xunleii
added a commit
that referenced
this issue
Jun 23, 2021
The use of `cluster_domain` is clearer than just` name`, which could be interpreted as something else. BREAKING CHANGE: Deprecation of `name` variable fix #53
xunleii
added a commit
that referenced
this issue
Jun 23, 2021
The use of `cluster_domain` is clearer than just` name`, which could be interpreted as something else. BREAKING CHANGE: Deprecation of `name` variable fix #53
xunleii
added a commit
that referenced
this issue
Jun 23, 2021
The use of `cluster_domain` is clearer than just` name`, which could be interpreted as something else. BREAKING CHANGE: Deprecation of `name` variable fix #53
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I do think it will be clearer if
var.name
is renamed incluster_domain
or similar.Get tricked by this until i realised that my services where all ending in
aws.cluster
:-)The text was updated successfully, but these errors were encountered: