Open steviecoaster opened 2 years ago
/cc @JPRuskin @Windos, will centralizing this break anything across the Azure Environment?
/cc @JPRuskin @Windos, will centralizing this break anything across the Azure Environment?
@steviecoaster our initial license package creation is embedded somewhere in the deployment of the environment, and our docs are "hey you've got a new license, here's how to update it" so centralizing it won't break anything.
General note, if something changes re naming/versioning the package we'd need to replicate that in the deployment and/or provide context in the Azure Environment specific docs.
This will impact that area, as there is a 4th version segment added to account for the node count the license is valid for as the 4th octet, so we should raise an issue on your end of things.
If you want, I can raise that issue an assign it to myself, although that's likely touching your template json and you might not want me touching that :joy:
What New Or Updated Would You Like To See?
Centralize documentation on creating a package for your C4B license
Why Is It Needed?
Docs for this are spread out across different sections of docs. If we update how we do things, we need to right now worry about editing several docs. If we centralize it into a fragment, we can then just link to that one central doc across all aspects and only need to make one change in the future
Additional Context?