Skip to content

Updates to allow for log folders to be directly in the root of a bucket - #14995

Open
gallen-ms wants to merge 5 commits into
Azure:masterfrom
gallen-ms:master
Open

Updates to allow for log folders to be directly in the root of a bucket#14995
gallen-ms wants to merge 5 commits into
Azure:masterfrom
gallen-ms:master

Conversation

@gallen-ms

Copy link
Copy Markdown

Change(s):

  • Updated MainTemplate.json,CiscoUmbrella_DataConnectorDefinition.json, and ReleaseNotes.md

Reason for Change(s):

  • When the folders are stored at the root of the bucket the s3BucketPrefix is not needed and no leading slash is required for the path. Made the field optional and updated markdown to explain when provided it should contain a trailing slash

Version Updated:

  • Yes

Testing Completed:

  • Need Help

Checked that the validations are passing and have addressed any issues that are present:

  • Need Help

Updated version numbers for solution and data connector. Updated connector to accept an empty s3BucketPrefix value and when provided the user should supply a trailing slash
Updated the release notes to include version 3.3.2 changes.
@gallen-ms
gallen-ms requested review from a team as code owners August 27, 2026 10:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the Cisco Umbrella solution to support Amazon S3 log folders located directly at the bucket root by making the S3 bucket prefix optional and adjusting prefix/path handling and guidance.

Changes:

  • Bumped solution/connector versions to 3.3.2 and added release notes entry.
  • Made s3BucketPrefix optional in the connector UI/template and updated instructional markdown.
  • Adjusted polling config path concatenation to avoid injecting a leading slash when prefix is empty.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
Solutions/CiscoUmbrella/ReleaseNotes.md Adds 3.3.2 release note describing optional prefix + trailing slash guidance.
Solutions/CiscoUmbrella/Package/mainTemplate.json Makes prefix optional, updates UI/help text, and updates prefix concatenation logic.
Solutions/CiscoUmbrella/Data/Solution_CiscoUmbrella.json Bumps solution version to 3.3.2.
Solutions/CiscoUmbrella/Data Connectors/CiscoUmbrella_CCP/CiscoUmbrella_PollingConfig.json Updates prefix concatenation for each log type path.
Solutions/CiscoUmbrella/Data Connectors/CiscoUmbrella_CCP/CiscoUmbrella_DataConnectorDefinition.json Makes prefix optional and adds guidance note + example update.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

"s3BucketName": "[[parameters('s3BucketName')]",
"s3BucketRegion": "[[parameters('s3BucketRegion')]",
"s3BucketPrefix": "[[concat(parameters('s3BucketPrefix'),'/auditlogs/')]",
"s3BucketPrefix": "[[concat(parameters('s3BucketPrefix'),'auditlogs/')]",
@@ -5875,8 +5887,8 @@
},
"s3BucketPrefix": {
"defaultValue": "s3BucketPrefix",
{
"type": "Markdown",
"parameters": {
"content": "> **NOTE:**\n> For Customer managed paths, you can leave the S3 Bucket Prefix empty if you want to use the root of the bucket. If you specify a prefix, make sure to include the trailing slash."
{
"type": "Markdown",
"parameters": {
"content": "> **NOTE:**\n> For Customer managed paths, you can leave the S3 Bucket Prefix empty if you want to use the root of the bucket. If you specify a prefix, make sure to include the trailing slash."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants