oam-dev
something about ApplicationScope
I am strange about how to create ApplicationScope, I find that it use ApplicationConfiguration custom resource define, it confuses me, could anyone tell me why do they not use a separate resource type
The idea is that an ApplicationConfiguration is the top level config for everything in OAM. You can create a scope by putting it in its own Application Configuration file, or you can put all of your components and scopes into one Application Configuration file and deploy it all together. If we had a separate top level resource type just for scopes, then you could no longer do the latter. The current approach seemed simpler.
I think it would help a lot if the ApplicationConfiguration as the top level config would simply be called Deployment. However, that would immediately cause confusement with K8s deployments in Rudr.
As more runtime implementations will become available, the chances of naming collisions with existing platform concepts will only increase though. Maybe the best way out is for OAM to add some prefixes, such as OAMDeployment, OAMComponent. Naming is hard... ;-)
