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

GR5: Allowed Location Check + Policy Compliance Status Information #181

Open
MathesonSho opened this issue Aug 13, 2024 · 3 comments
Open
Assignees
Labels
enhancement New feature or request Iteration #1 Before V2.0 go-live PriorityForAssignees -Next V2.0 Applicable for updating to v2.0

Comments

@MathesonSho
Copy link
Contributor

Current check determines if the policy/ initiative has been applied across the tenant, that the parameters are correct and that there are no exemptions. Request is to add policy logic that also incorporates policy/initiative resource compliance into the CaC's control status of compliant or non-compliant.

For example: If a subscription has the allowed location policy applied after already creating a resource in Europe. The resource remains in Europe and the policy dashboard will show that non-compliant resource. The solutions check should then return. "Non-compliant. The policy has been applied, however 1 resource is non-compliant. "

Logic Change applied to GR6 as a reference. Include the same comment logic to explain issues to the client.
#139

@MathesonSho MathesonSho added enhancement New feature or request V2.0 Applicable for updating to v2.0 labels Aug 13, 2024
@dutt0 dutt0 added the Iteration #2 After V2.0 go-live label Aug 20, 2024
@MathesonSho
Copy link
Contributor Author

MathesonSho commented Oct 18, 2024

@dutt0 Can this be completed sooner? Iteration #1 focused on adding the ability to use an initiative- however the improvements are still needed to be updated to sync with GR6's progress. The current format is hard to test/ understand as it still includes management groups and it has duplication of MGs. One compliant and non-compliant. Would be beneficial to update.

@dutt0
Copy link
Contributor

dutt0 commented Nov 21, 2024

We can prioritize this tickets in the first phase of iteration#2

@MathesonSho MathesonSho added Iteration #1 Before V2.0 go-live and removed Iteration #2 After V2.0 go-live labels Dec 10, 2024
@MathesonSho
Copy link
Contributor Author

Before Go-Live please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Iteration #1 Before V2.0 go-live PriorityForAssignees -Next V2.0 Applicable for updating to v2.0
Projects
None yet
Development

No branches or pull requests

3 participants