{Containerapp} Fix Credential Scanner failed#32274
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
Pull Request Overview
This PR addresses a Credential Scanner security issue by replacing potentially sensitive authentication keys in test recording files with placeholder values.
- Replaces actual
sharedKeyvalues in test recordings with a sanitized placeholder "abc123" - Maintains consistent formatting across all test recording files
- Ensures test recordings don't contain real credentials that could trigger security scanners
Reviewed Changes
Copilot reviewed 19 out of 19 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| test_containerapp_up_source_with_dockerfile_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_up_image_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_tcp_ingress.yaml | Replaced shared key with placeholder value |
| test_containerapp_get_customdomainverificationid_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_update_custom_domains.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_p2p_traffic_encryption.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_mtls.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_logs_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_internal_only_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_custom_domains.yaml | Replaced shared key with placeholder value |
| test_containerapp_env_certificate_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_custom_domains_e2e.yaml | Replaced shared key with placeholder value |
| test_containerapp_create_with_vnet_yaml.yaml | Replaced shared key with placeholder value |
| test_containerapp_create_with_environment_id.yaml | Replaced shared key with placeholder value |
| test_containerapp_compose_create_environment_to_target_location.yaml | Replaced shared key with placeholder value |
| test_container_app_mount_secret_update_e2e.yaml | Replaced shared key with placeholder value |
| test_container_app_mount_secret_e2e.yaml | Replaced shared key with placeholder value |
| test_container_app_mount_azurefile_e2e.yaml | Replaced shared key with placeholder value |
Comments suppressed due to low confidence (16)
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Seems the CI failed not related to this PR's change: |
|
We definitely need a replacer to do this. Otherwise, rerunning these tests will generate valid |
Hi @jiasli
|
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
evelyn-ys
left a comment
There was a problem hiding this comment.
Instead of manually replacing keys, can you implementing a test recording replacer to automatically do that?
Yes, we need a permanent solution for this. We fixed the same issue before in #32232 |
|
Next Tuesday is the code freeze. To unblock the release, shall we merge this PR first? @evelyn-ys @Greedygre will create another PR to add the replacer. |
|
There a new format of credential fixed in #32340 |
Related command
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.