Skip to content

Commit

Permalink
chore(main): Release transformation-azure-compliance-free v1.3.0
Browse files Browse the repository at this point in the history
  • Loading branch information
cq-bot committed Dec 20, 2023
1 parent d1b3a86 commit 737c4bd
Show file tree
Hide file tree
Showing 3 changed files with 36 additions and 34 deletions.
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"transformations/aws/compliance-free+FILLER": "0.0.0",
"transformations/aws/compliance-premium": "0.4.0",
"transformations/aws/compliance-premium+FILLER": "0.0.0",
"transformations/azure/compliance-free": "1.2.3",
"transformations/azure/compliance-free": "1.3.0",
"transformations/azure/compliance-free+FILLER": "0.0.0",
"transformations/azure/compliance-premium": "0.1.3",
"transformations/azure/compliance-premium+FILLER": "0.0.0",
Expand Down
14 changes: 14 additions & 0 deletions transformations/azure/compliance-free/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,19 @@
# Changelog

## [1.3.0](https://github.com/cloudquery/policies-premium/compare/transformation-azure-compliance-free-v1.2.3...transformation-azure-compliance-free-v1.3.0) (2023-12-20)


### Features

* Trigger GCP Free Build Transformations ([5c68bae](https://github.com/cloudquery/policies-premium/commit/5c68bae0f30e4e57db5774300488d4b6ddd42c3b))
* Trigger GCP Free Build Transformations ([#385](https://github.com/cloudquery/policies-premium/issues/385)) ([5c68bae](https://github.com/cloudquery/policies-premium/commit/5c68bae0f30e4e57db5774300488d4b6ddd42c3b))


### Bug Fixes

* Link to latest versions in README ([#428](https://github.com/cloudquery/policies-premium/issues/428)) ([44901a2](https://github.com/cloudquery/policies-premium/commit/44901a2be3ada54606fc928010ae9a15aaff7173))
* Updated dbt_run without specifying the model ([#422](https://github.com/cloudquery/policies-premium/issues/422)) ([b7ff919](https://github.com/cloudquery/policies-premium/commit/b7ff91978bd67ef1b859d6aaa012beef1ea84181))

## [1.2.3](https://github.com/cloudquery/policies-premium/compare/transformation-azure-compliance-free-v1.2.2...transformation-azure-compliance-free-v1.2.3) (2023-12-05)


Expand Down
54 changes: 21 additions & 33 deletions transformations/azure/compliance-free/dbt_project.yml
Original file line number Diff line number Diff line change
@@ -1,35 +1,23 @@
# Name your project! Project names should contain only lowercase characters
# and underscores. A good package name should reflect your organization's
# name or the intended use of these models
name: "azure_compliance"
version: "1.0.0"
name: azure_compliance
version: 1.3.0
config-version: 2

# This setting configures which "profile" dbt uses for this project.
profile: "azure_compliance"

# These configurations specify where dbt should look for different types of files.
# The `model-paths` config, for example, states that models in this project can be
# found in the "models/" directory. You probably won't need to change these!
model-paths: ["models", "../models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["../macros", "../../macros"]
snapshot-paths: ["snapshots"]

clean-targets: # directories to be removed by `dbt clean`
- "target"
- "dbt_packages"

# Configuring models
# Full documentation: https://docs.getdbt.com/docs/configuring-models

# In this example config, we tell dbt to build all models in the example/
# directory as views. These settings can be overridden in the individual model
# files using the `{{ config(...) }}` macro.
profile: azure_compliance
model-paths:
- models
- ../models
analysis-paths:
- analyses
test-paths:
- tests
seed-paths:
- seeds
macro-paths:
- ../macros
- ../../macros
snapshot-paths:
- snapshots
clean-targets:
- target
- dbt_packages
models:
azure_compliance:
# Config indicated by + and applies to all files under models/example/
# example:
# +materialized: view
azure_compliance: null

0 comments on commit 737c4bd

Please sign in to comment.