🚀 Feature Request

Is your feature request related to a problem? Please describe.

The problem is more on user's usability, where the user has to know (and copy-paste) the whole rule string in the "ruleName" text box in order to list the resources affected by that rule.

This should be a prepopulated drop-down multi-select field like the "Resource Name" in the "Azure DevOps Rule Hits by Resource" Workbook.

Also, the Resource FQN Column which lists the selected resource's rule Outcome(s), should be a hyperlink taking the user to the Resource Rule details screen (like in the Azure DevOps Resource State Workbook)

There are two usability problems here:

1. The user need to know the rule name, the specific rule FQN, copy it from somewhere and then paste it in the "ruleName" field
2. The table gets populated with that rule's Resource FQN and Outcome, but then the user does not know what the next action should be. I guess the logical action should be for the Resource FQN which either pass or fails, to be a hyperlink that sends the user to that Resource's Rule details screen. This is just a suggestion for analysis and review based on my perspective

---

Describe the solution you'd like

---

Describe alternatives you've considered

---

Additional context

🐞 Bug Report

Describe the bug

Probably this happens because the Vault name defined in the Bicep template is static and the location is hard coded to western europe, where this vault already exists. Maybe add a random suffix in the vault's name?

---

Is this a regression?

---

To Reproduce

---

Expected behaviour

---

Media prove

---

Your environment

• OS:
• PowerShell version:
• PSRule version:
• PSRule.Rules.AzureDevOps version:

---

Additional context

🐞 Bug Report

Describe the bug

From the Resource Name drop-down multi-select field, if I select more than one resource to be displayed, then I get a query error. Error's Line and Position # differs based on the drop-down resource selection. The "All" and "single-select" checkbox options work.

---

Is this a regression?

This is the first time I am experiencing this since the initial deployment and initial run of the YAML Pipeline

---

To Reproduce

---

Media prove

---

Your environment

• OS:
• PowerShell version:
• PSRule version:
• PSRule.Rules.AzureDevOps version:

---

Additional context

🐞 Bug Report

Describe the bug

The Azure location 'West Europe' is hard-coded in the resource deployment of the bicep template. For example I have created my RG in 'eastus' and I need all my resources to be created in 'eastus'. However, the resources are created by default in 'west europe'. May have the $location as input variable in the 'az deployment group create' script for the main.bicep?

---

Is this a regression?

---

To Reproduce

---

Expected behaviour

---

Media prove

---

Your environment

• OS:
• PowerShell version:
• PSRule version:
• PSRule.Rules.AzureDevOps version:

---

Additional context