* Basic support for C4 model primitives.
* Use the "rect" shape for nodes
With the record shape we used before, graphviz would trip over
edges that set constraint=False.
* Adopt C4 terminology: Rename Dependency -> Relationship
* Adopt C4 terminology: Rename type -> technology
* Extract a shared C4Node
This makes the code more DRY, but also allows to add company-
specific extensions more easily. One need we have is to slightly
adapt the terminology. At Spotify, we happen to call `Container`
a `Component` for example. This is now easier to implement on top
of the shared `C4Node`.
* Add "C4" shield to the README
* Document how to produce a C4 diagram
* Update readme
One proposition of change for the presentation, listing 6 cloud providers is already out of date as new cloud providers was added and will be added in future.
I put a more generic sentence. So no need to update the readme each time a new provider is added.
I think that there's no need to list all providers as the badges just above list them.
I also added saas and programming I tried to be generic so here also no need to update the readme when adding new resources.
I hope I didn't misspell words and my grammar is correct.
* Fix space
* Add Icon set for Oracle Cloud Services. Update scripts to handle the new provider
* feat: add alibaba cloud resources
* chore: delete unused script
* bump: up to version 0.4.0
* docs: add alibaba cloud
* chore: make a publish script executable
* docs: update menus for alibaba cloud
* Code cleanup per pull request feedback
* Add Oracle cloud to website and command line to generate the classes
* Add missing module script for OCI provider
Co-authored-by: Prodesire <Prodesire@yeah.net>
Co-authored-by: MinJae Kwon <mingrammer@gmail.com>