FQDN up to 25 characters

[kagarmoe]

Signed-off-by: kagarmoe kgarmoe@chef.io

🔩 Description: What code changed, and why?

Define the length of the FQDN in the configurations doc.
Includes some linting cleanup.

⛓️ Related Resources

#4890

👍 Definition of Done

👟 How to Build and Test the Change

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[netlify]

Deploy preview for chef-automate ready!

Built with commit 112f00c

https://deploy-preview-4900--chef-automate.netlify.app

[msorens]

Lost a subject in there.

Suggested change

	The maximum size of a customized fully qualified domain name (FQDN) is 25 characters. To change the of your Chef Automate installation, create a TOML file that contains the partial configuration:
	The maximum size of a customized fully qualified domain name (FQDN) is 25 characters. To change the FQDN of your Chef Automate installation, create a TOML file that contains the partial configuration:

[msorens]

Good guess, but, well, not so much. There is no limit on the size of the whole FQDN string.
The 25-character limit is only after the final dot, so something like this is invalid:
http://www.foo.this-portion-is-probably-too-long

[kagarmoe]

@SEAjamieD So 25 characters for the top-level domain?

http://www.foo.this-portion-is-probably-too-long
<scheme>://<subdomain>.<second-level domain>.<top-level domain>

[SEAjamieD]

@kagarmoe - Correct, thank you!

[SEAjamieD]

Pending and update for @msorens comment below, this is good for our needs. Thanks so much!

There is no limit on the size of the whole FQDN string.
The 25-character limit is only after the final dot, so something like this is invalid:
http://www.foo.this-portion-is-probably-too-long