Eric Sauer
Eric Sauer
@aelicieguo I don't think we would recommend blanket applying the baseline policies against pre-existing namespaces, but instead applying it to all _new_ projects (i.e. application projects), possibly via a default...
@sabre1041
@buuhsmead agreed. There's an open PR in our toolkit repo that provides some of this https://github.com/redhat-cop/openshift-toolkit/pull/36. Once that gets merged, we will move toward building on the guidance in the...
https://github.com/ianwatsonrh/grafana-namespace-app
@logandonley sounds great. Let's figure out an mvp skeleton of some kind that we can get merged into the repo so that we can do PRs in small chunks.
@sherl0cks I know i've harped on this before, but I don't see a big need to productize this. We should teach "applier" as if its a pattern, not a tool,...
@pcarney8 @sabre1041 agree. a katacoda quickstart would be wicked.
Latest directory structure proposal from conversation with @pcarney8 and @logandonley : ``` project_root/ .openshift/
@oybed - the reason for the hidden directories is that that's the convention elsewhere in the openshift space.. i.e. `.openshift/` is where you place your openshift resources in a repo...
All that to said, I don't ever intend to treat of of the directory stucture stuff as "These are the rules", just "this is a convention to help you build...