Skip to content

Commit

Permalink
Bump Dependencies (#804)
Browse files Browse the repository at this point in the history
* Update RequiredVersion

* Update
  • Loading branch information
Jefajers authored May 31, 2023
1 parent 43b781d commit 7c32e85
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
6 changes: 3 additions & 3 deletions docs/wiki/Custom-Jq-Templates.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,11 @@ As a part of **AzOps Pull**, information retrieved from Azure is converted into

For scenarios where you need to customize the information filtered or its structure, AzOps supports the use of *bring your own templates* by configuring two settings: `Core.SkipCustomJqTemplate` and `Core.CustomJqTemplatePath`.

The setting `Core.SkipCustomJqTemplate` represents the flag to enable (`$false`) or disable (`$true`) the capability and `Core.CustomJqTemplatePath` is the path to the folder location of your custom templates (default's to `.customtemplates`).
The setting `Core.SkipCustomJqTemplate` represents the flag to enable (`false`) or disable (`true`) the capability and `Core.CustomJqTemplatePath` is the path to the folder location of your custom templates (default's to `.customtemplates`).

## Logic

What happens? when the following is set: `"Core.SkipCustomJqTemplate": true` and `"Core.CustomJqTemplatePath": ".customtemplates"`.
What happens, when the following is set: `"Core.SkipCustomJqTemplate": true` and `"Core.CustomJqTemplatePath": ".customtemplates"`?

For retrieved resources, AzOps will look for a matching template file in the custom location. If no match is found AzOps falls back to [built-in templates](https://github.com/Azure/AzOps/tree/main/src/data/template).

Expand All @@ -36,7 +36,7 @@ AzOps performs transformation of pulled information in three high level steps.
* Look for folder matching `providerNamespace` and a file matching `resourceTypeName`.template.jq
* If no match found default to `template.jq` at given template folder root

Example of custom templates for `policyExemptions`, would result in `policyExemptions` resources being transformed with custom templates (according to step 1 and 3 above) and all other resources being transformed with built-in:
Example of custom templates for `policyExemptions`, resulting in `policyExemptions` resources being transformed with custom templates (according to step 1 and 3 above) and all other resources being transformed with built-in:
```bash
.customtemplates
└── Microsoft.Authorization
Expand Down
8 changes: 4 additions & 4 deletions src/AzOps.psd1
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
#
# Generated by: Customer Architecture Team (CAT)
#
# Generated on: 4/21/2023
# Generated on: 5/30/2023
#

@{
Expand Down Expand Up @@ -52,10 +52,10 @@ PowerShellVersion = '7.2'

# Modules that must be imported into the global environment prior to importing this module
RequiredModules = @(@{ModuleName = 'PSFramework'; RequiredVersion = '1.7.270'; },
@{ModuleName = 'Az.Accounts'; RequiredVersion = '2.12.2'; },
@{ModuleName = 'Az.Billing'; RequiredVersion = '2.0.1'; },
@{ModuleName = 'Az.Accounts'; RequiredVersion = '2.12.3'; },
@{ModuleName = 'Az.Billing'; RequiredVersion = '2.0.2'; },
@{ModuleName = 'Az.ResourceGraph'; RequiredVersion = '0.13.0'; },
@{ModuleName = 'Az.Resources'; RequiredVersion = '6.6.1'; })
@{ModuleName = 'Az.Resources'; RequiredVersion = '6.7.0'; })

# Assemblies that must be loaded prior to importing this module
# RequiredAssemblies = @()
Expand Down

0 comments on commit 7c32e85

Please sign in to comment.