Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As RAM user, I want Owner and Resolver field to be always populated so that the % of assigned non compliance is increased so that the % of resolution is improved too #58

Open
BrunoReboul opened this issue Oct 11, 2020 · 1 comment
Labels
type: enhancement Existing feature improvement
Milestone

Comments

@BrunoReboul
Copy link
Owner

Always populated means:

  • Have a yaml content providing owner and resolver identity for a given folder ID or org ID (aka address missing gcp label on folder and orgs)
  • When a resources does not have a owner of resolver label, use the parent project's owner and resolver label
  • When a project does not have a owner of resolver label, use the parent folder's owner and resolver provided in the yaml content
  • When a folder does not have a owner of resolver label, use the parent folder's owner and resolver provided in the yaml content

Good practice, at least have owner and resolver described to each top level folders

To deal with emails in label value:

  • replace _dot_ by .
  • replace _at_ by @
    example: marie-pierre_dot_dupondt_at_mycompany_dot_com translates to marie-pierre.dupondt@mycompany.com

Update the DataStudio report template accordingly to leverage owner and resolver

@BrunoReboul BrunoReboul added the type: enhancement Existing feature improvement label Oct 11, 2020
@BrunoReboul BrunoReboul added this to the Backlog milestone Oct 11, 2020
@MarcFundenberger
Copy link

There is new feature called "Essential Contact" (in preview).
Perhaps this could be of use here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Existing feature improvement
Projects
None yet
Development

No branches or pull requests

2 participants