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

Policy bug when changing initiative profilename values #478

Closed
scottsla opened this issue Mar 26, 2021 · 3 comments · Fixed by #1059
Closed

Policy bug when changing initiative profilename values #478

scottsla opened this issue Mar 26, 2021 · 3 comments · Fixed by #1059
Assignees
Labels
bug Something isn't working policy

Comments

@scottsla
Copy link

scottsla commented Mar 26, 2021

When you specify a different profilename in diagnostic initiative the deployifnotexists correctly uses this however the setbypolicy value is hard coded on the compliance check so compliance checks then fail even though the policy has correctly remediated item. simply change of the name utilising the profilename parameter corrects the issue.

@krnese
Copy link
Contributor

krnese commented Apr 6, 2021

Thanks for flagging this. We will correct this in upcoming PR.

@jtracey93
Copy link
Collaborator

Trigger ADO Sync 1

@jtracey93
Copy link
Collaborator

Trigger ADO Sync 2

@jfaurskov jfaurskov linked a pull request Oct 7, 2022 that will close this issue
@jtracey93 jtracey93 assigned jfaurskov and unassigned MathieuRietman and krnese Oct 7, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Nov 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working policy
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants