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

#695 Fixing admin email length to fit RFC 3696, Errata 1003 #2269

Merged
merged 1 commit into from Jun 6, 2016

Conversation

Projects
None yet
3 participants
@tedops

tedops commented Jun 6, 2016

According to the IETF, RFC 3696 in Errata 1003 states that email address lengths are to be 254 octets. This is a fix to both follow that standard and fix the root of issue #695.

@ketan

This comment has been minimized.

Show comment
Hide comment
@ketan

ketan Jun 7, 2016

Contributor

Would we not "fix" this in the XSD as well?

Contributor

ketan commented Jun 7, 2016

Would we not "fix" this in the XSD as well?

tedops pushed a commit to tedops/gocd that referenced this pull request Jun 7, 2016

@tedops

This comment has been minimized.

Show comment
Hide comment
@tedops

tedops Jun 7, 2016

Hey @ketan - that's a good callout, and as I was submitting a PR to add that, I noticed @arvindsv already had one cooking.

The cruise-config.xsd didn't previously have any length restriction defined for emailType, which is why this PR was originally only to change the Ruby template. However, I do agree that being explicit is better than implicit, and therefore support Aravind's above linked PR.

tedops commented Jun 7, 2016

Hey @ketan - that's a good callout, and as I was submitting a PR to add that, I noticed @arvindsv already had one cooking.

The cruise-config.xsd didn't previously have any length restriction defined for emailType, which is why this PR was originally only to change the Ruby template. However, I do agree that being explicit is better than implicit, and therefore support Aravind's above linked PR.

@arvindsv arvindsv modified the milestone: Release 16.6 Jun 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment