| Key: |
QB-3895
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Krzysztof Balinski
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 11/Oct/22 06:16 AM
Updated: 21/Jan/23 01:15 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
12.0.21,
13.0.2
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
azure plugin, nodes
|
|
|
Currently QB azure plugin uses unique resource groups for new created resources (nodes).
From access management point of view and from cost estimation would be good to specify one single resource group (pre-defined) in cloud profile.
Would it be possible to statically pre-define static resource group per cloud profile - in that aproach all new resources (nodes) would land in one single azure resource group.
|
|
Description
|
Currently QB azure plugin uses unique resource groups for new created resources (nodes).
From access management point of view and from cost estimation would be good to specify one single resource group (pre-defined) in cloud profile.
Would it be possible to statically pre-define static resource group per cloud profile - in that aproach all new resources (nodes) would land in one single azure resource group. |
Show » |
| No work has yet been logged on this issue.
|
|
AZURE plugin node assigment to static resource group