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

Azure CosmosDB SQL & MongoDB #15

Merged
merged 24 commits into from
Sep 17, 2024
Merged
Changes from 1 commit
Commits
Show all changes
24 commits
Select commit Hold shift + click to select a range
40c6c3f
initial helper modules
mattJsonar Sep 4, 2024
b05318d
create azure sql server module
mattJsonar Sep 6, 2024
67806b9
remove database extended policy
mattJsonar Sep 6, 2024
1e9ec15
Apply automatic changes
mattJsonar Sep 6, 2024
e334235
remove azure cloud account module
mattJsonar Sep 6, 2024
dd5dc8d
terraform-docs: automated action
github-actions[bot] Sep 6, 2024
63fb3d3
typo
mattJsonar Sep 10, 2024
371234f
add cosmos sql module
mattJsonar Sep 11, 2024
e601f65
add cosmos mongo module
mattJsonar Sep 12, 2024
2eb48ca
add cosmos modules to version list
mattJsonar Sep 12, 2024
22ce093
Azure SQL Server: split eventhub creation into separate module (#14)
mattJsonar Sep 14, 2024
3a7f9a9
fix wording
mattJsonar Sep 16, 2024
1245c00
Merge branch 'matt/SR-1732-azure-sql-server' into matt/SR-1728-azure-…
mattJsonar Sep 16, 2024
c7eb78c
support many-to-one
mattJsonar Sep 16, 2024
78569d8
Merge branch 'main' into matt/SR-1728-azure-cosmos-sql
mattJsonar Sep 17, 2024
170321a
terraform-docs: automated action
github-actions[bot] Sep 17, 2024
1fc7ed5
remove mentions of sql server
mattJsonar Sep 17, 2024
bd39aef
remove angle brackets
mattJsonar Sep 17, 2024
a46ee2f
cleanup variables
mattJsonar Sep 17, 2024
e6c567a
1.0.6 release date
mattJsonar Sep 17, 2024
df9949f
terraform-docs: automated action
github-actions[bot] Sep 17, 2024
ee2f831
resolve comments
mattJsonar Sep 17, 2024
113c630
resolve comments 2
mattJsonar Sep 17, 2024
e3d7922
terraform-docs: automated action
github-actions[bot] Sep 17, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
resolve comments
  • Loading branch information
mattJsonar committed Sep 17, 2024

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
commit ee2f831af5df624505b8c3bfaa841a833e8c89dd
4 changes: 2 additions & 2 deletions examples/onboard-azure-cosmosdb-mongo/README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Onboard Azure Cosmos DB API for MongoDB example
This example includes additional prerequisites that will need to be completed to fully utilize the module. More details can be found in the [onboarding documentation](https://docs.imperva.com/bundle/onboarding-databases-to-sonar-reference-guide/page/Azure-Cosmos-DB-API-for-MongoDB-Onboarding-Steps_48367240.html).

This example creates 'azurerm' and 'dsfhub' resources. More infomation regarding authentication to each can be found in the relevant provider documentation:
This example creates 'azurerm' and 'dsfhub' resources. More information regarding authentication to each can be found in the relevant provider documentation:
- [azurerm](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs)
- [dsfhub](https://registry.terraform.io/providers/imperva/dsfhub/latest/docs)

@@ -12,7 +12,7 @@ This module expects an Event Hub and a Storage Account Container to have been cr
Cosmos DB audit logs are sent to an Azure Event Hub and are retrieved by DSF. The Event Hubs are created within an Event Hub Namespace, which can contain one or more Event Hubs. Audit logs of multiple Cosmos DB instances can be sent to a single Event Hub.

### Azure Storage Account and Container
Storage Containers are used to store transactional data for the Event Hub import processes, and one Storage Container is required for each Event Hub. These Storage Containers exists within a Storage Account, which may contain multiple Storage Containers.
Storage Containers are used to store transactional data for the Event Hub import processes, and one Storage Container is required for each Event Hub. These Storage Containers exist within a Storage Account, which may contain multiple Storage Containers.

<!-- BEGIN_TF_DOCS -->
## Requirements
4 changes: 2 additions & 2 deletions examples/onboard-azure-cosmosdb-sql/README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Onboard Azure Cosmos DB SQL API example
This example includes additional prerequisites that will need to be completed to fully utilize the module. More details can be found in the [onboarding documentation](https://docs.imperva.com/bundle/onboarding-databases-to-sonar-reference-guide/page/Azure-Cosmos-DB-SQL-API-Onboarding-Steps_48367255.html).

This example creates 'azapi', 'azurerm' and 'dsfhub' resources. More infomation regarding authentication to each can be found in the relevant provider documentation:
This example creates 'azapi', 'azurerm' and 'dsfhub' resources. More information regarding authentication to each can be found in the relevant provider documentation:
- [azapi](https://registry.terraform.io/providers/Azure/azapi/latest/docs)
- [azurerm](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs)
- [dsfhub](https://registry.terraform.io/providers/imperva/dsfhub/latest/docs)
@@ -13,7 +13,7 @@ This module expects an Event Hub and a Storage Account Container to have been cr
Cosmos DB audit logs are sent to an Azure Event Hub and are retrieved by DSF. The Event Hubs are created within an Event Hub Namespace, which can contain one or more Event Hubs. Audit logs of multiple Cosmos DB instances can be sent to a single Event Hub.

### Azure Storage Account and Container
Storage Containers are used to store transactional data for the Event Hub import processes, and one Storage Container is required for each Event Hub. These Storage Containers exists within a Storage Account, which may contain multiple Storage Containers.
Storage Containers are used to store transactional data for the Event Hub import processes, and one Storage Container is required for each Event Hub. These Storage Containers exist within a Storage Account, which may contain multiple Storage Containers.
<!-- BEGIN_TF_DOCS -->
## Requirements

Loading
Oops, something went wrong.