text:
[Key Vault] Update metadata for release

This also adds two typehint comments to pass mypy inspection for Administration.

/azp run python - keyvault - ci

/check-enforcer override


text:
[AutoPR compute/resource-manager] Added Eviction Policy Property for VirtualMachineScaleSetVMProfile for version 2017-12-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2836

(message created by the CI based on PR content)

Codecov Report

Merging #2364 into restapi_auto_compute/resource-manager will increase coverage by <.01%.
The diff coverage is 100%.

@@                            Coverage Diff                            @@
##           restapi_auto_compute/resource-manager    #2364      +/-   ##
=========================================================================
+ Coverage                                  54.25%   54.25%   +<.01%
=========================================================================
  Files                                       5330     5330
  Lines                                     126697   126701       +4
=========================================================================
+ Hits                                       68737    68741       +4
  Misses                                     57960    57960

Impacted Files
Coverage Δ

.../azure/mgmt/compute/v2017_12_01/models/__init__.py
84.94% <ø> (ø)
:arrow_up:

...17_12_01/models/compute_management_client_enums.py
100% <100%> (ø)
:arrow_up:

..._01/models/virtual_machine_scale_set_vm_profile.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0affd3d...fe7e19d. Read the comment docs.

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2276

source: gharchive/pull-request

authors: AutorestCI codecov-io

repo: Azure/azure-sdk-for-python

license: MIT

license_type: permissive

license_source: github-api


text:
Update webpubsub from Language-Settings.ps1

fix https://github.com/Azure/azure-sdk-for-python/issues/21346

/azp run - core - ci


text:
[Storage] Prepare for STG93 Beta Release (changelog dates, etc.)

As title states.

API change check
API changes are not detected in this pull request.

authors: azure-sdk vincenttran-msft


text:
Adding classes for Token Statistics

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml

Check the Build/Analyze PR gate failure. My PR for the pylint/black fixes should be in by EOD 4/26, but this PR has introduced failures for MyPy which is Python's type checker, so you'll need to address those.

authors: achauhan-scc azure-sdk diondrapeck


text:
[AutoPR web/resource-manager] WebApps: Snapshots API for DR stamps

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4291

(message created by the CI based on PR content)


text:
[Key Vault] Generate Certificates with TypeSpec

Description
Generated with the spec from https://github.com/Azure/azure-rest-api-specs/pull/28708.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

authors: azure-sdk mccoyp


text:
Adding ID placeholder for evaluators

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

authors: azure-sdk singankit


text:
Storage examples are out of date?

Hi I have code from example:
pub async fn upload_blob(container: &str, blob_path: &str, blob: &str) -> Result<bool, Box<dyn Error>> {
    println!("{}", container);
    println!("{}", blob_path);
    println!("{}", blob);

    let container = get_container_client(container);
    container.create();

    let blob_client = container.blob_client(blob_path);

    let res = blob_client
        .put_block_blob("121431241241")
        .content_type("text/plain").await?;

    println!("1-put_block_blob {:?}", res);

    return Ok(true);
}

But after this I get error:

   |
73 |         .content_type("text/plain").await?;
   |                                    ^^^^^^
   |                                    |
   |                                    `PutBlockBlobBuilder` is not a future
   |                                    help: remove the `.await`
   |
   = help: the trait `std::future::Future` is not implemented for `PutBlockBlobBuilder`

This is code from example, I'm I missing something ? I use latest 0.6.0 version. When I remove .await it compiles bot code don't work nothing is written on storage (also container.create() don't work with await, and example has await).
Storage account is also fine, reading examples works.

Ok I figured, you have to add "into_futures" features to your cargo.toml
azure_storage_blobs = { version = "0.6.0", features = ["into_future"] }

Correct, the version on the main branch is the absolute latest version and differs a bit from the release on crates.io. We release currently on a monthly basis so eventually this inconsistency corrects itself.

source: gharchive/issue

repo: Azure/azure-sdk-for-rust


text:
[Breaking Change] Report should link to prior preview with approved breaking changes

Breaking changes approved in a preview version will be flagged for review in all subsequent api-versions until they finally make it to a GA version. These redundant reviews are wasteful, consuming reviewer time and slowing down service teams.
In an ideal world such "re-appovals" would be automated, but that would require checking that no new breaking changes were introduced in the new api-version. However, there is part of the process that could be automated -- checking for a prior preview, finding the relevant PR, and checking to see if it has approved breaking changes.
Specifically, I would like the Breaking Changes report to add a message near the top of the report -- only added when there is a prior preview with approved breaking changes -- that says something like:

Breaking changes may have been previously approved in [PR link].

There is an email thread, Re: Breaking Changes for Microsoft.Sql 2023-02-01-preview Version Release, with @jeremyfrosti where this issue is particularly acute. That is: Jeremy pushed many updates to their dev release* branch resulting in reviews. Then when finally merging the dev branch to main, in this PR:

https://github.com/Azure/azure-rest-api-specs/pull/25293

The breaking changes were reported all over again. Jeremy had to resort to manually compiling a table of all the previous PRs where appropriate breaking changes have been already approved.
Note there is a related issue where we want to disable mandatory reviews (just the reviews, not the checks) of breaking changes on PRs to dev branch:

https://github.com/Azure/azure-sdk-tools/issues/5838

This way users would still get feedback early, but the formal breaking change review would happen only once, when merging the dev branch to main.

Additional context in Teams, here.

authors: konrad-jamrozik mikekistler

repo: Azure/azure-sdk-tools


text:
[APIView][Feature Request] Consolidate review comments and send one email notification

Currently, an email notification is sent for each comment on the APIView. It would be nice to provide an option to consolidate all comments into a single notification and then submit the review.

We are running out of our free email monthly quota. This change will help us reduce email usage.

authors: praveenkuttappan srnagar


text:
Support no baseline issue.

Js removes its baseline recently which failed the analysis step.
Failed pipeline: https://dev.azure.com/azure-sdk/public/_build/results?buildId=1420643&view=logs&j=90227089-9f51-5ecc-566c-84e1f2918394&t=7da0f684-6369-5290-bb0b-5d27f59dde66
Need to add check for no baseline case.
Testing pipeline: https://dev.azure.com/azure-sdk/public/_build/results?buildId=1421019&view=logs&j=bc67675d-56bf-581f-e0a2-208848ba68ca&t=7eee3a58-6120-518b-7fcb-7e943712aa81

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

We can simply remove the baseline parameter in js repo. Closed the PR as it is not needed.

authors: azure-sdk sima-zhu


text:
Change Request:  for

Thank you for contributing to the design guidelines for Azure SDKs.  We welcome all discussions and contributions.  Since the design guidelines affect the client libraries for all Azure services, we thoroughly discuss and vet any design guideline changes before we incorporate them into the official guidance.  This process can take some time, so your patience is appreciated.
** Before submitting, ensure you adjust the title of the issue appropriately **
The Basics

Which design guideline is affected?

Which target languages are affected?

Describe the change:

Reasoning
Please provide any additional detail or reasoning for the request.

@kyle-patterson @lilyjma this looks like a spam issue. If that is not the case please feel free to reopen.

repo: Azure/azure-sdk


text:
azcopy aborts if file is updated after copy started

Which version of the AzCopy was used?
10.14.0
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
azcopy copy [local file pat] [storage container] --recursive
What problem was encountered?
We are using azcopy to copy snapshot of log files that are being written into. We have been using gsutil on google for the same and it works perfectly fine. AzCopy however aborts when it detects that last modified time has changed after copy started.
How can we reproduce the problem in the simplest way?
unit tests already capture this seems like:
https://github.com/Azure/azure-storage-azcopy/blob/aedcd0b00711650f0acaf43f69bcb08a0c26e578/e2etest/zt_change_detection_test.go#L34
seems below code is triggering this:
https://github.com/Azure/azure-storage-azcopy/blob/aedcd0b00711650f0acaf43f69bcb08a0c26e578/ste/xfer-anyToRemote-file.go#L304
create a large file using dd or some other cmd.
start azcopy to copy it to some storage container
append something to the file or do some operation to update the last modified time.
Have you found a mitigation/solution?
Ideal solution it seems could be that there is an option to bypass this check.
We have to currently first use linux cp command to copy to a local staging directory and then use azcopy to copy from the staging directory to a storage container. This is problematic in long run for us as a) it adds to overall elapsed time b) the local storage space is in demand for other things

Hi @dskdas, this is expected behaviour, files updated on while being transferred cause data inconsistency on the destination. This feature will be retained.

authors: dskdas nakulkar-msft

repo: Azure/azure-storage-azcopy


text:
Added error message to failed transfer details.

Refer to the following commit https://github.com/Azure/azure-storage-azcopy/commit/b7993f7edaf49f2dd33d3faa1aa97e910b2fc0df from the PR https://github.com/Azure/azure-storage-azcopy/pull/1745

add error message to JobPartPlanTransfer and failed transfer details

change jobstatus of 403 errors from Cancelled to Failed

use atomic operations for errormessage length

check error message does not exceed max length

A new PR has been created in order to make the changes more modular, and easily reviewable.

Azcopy team anyway going to implement error message handling for each file. This PR is not much useful in that case. We dropping this change as its not space efficient.

authors: Strikerzee nitin-deamon


text:
Contribute StorageAccount module - Closes #97

Description
Contribute module CARML module StorageAccounts with issue #97 .
Adding a new module

[x] A proposal has been submitted and approved.
[x] I have included "Closes #{module_proposal_issue_number}" in the PR description.
[x] I have run brm validate locally to verify the module files.
[x] I have run deployment tests locally to ensure the module is deployable.

Successful test
> New-AzResourceGroupDeployment -ResourceGroupName 'test-Rg' -TemplateFile '.\test\main.test.bicep' -Verbose
VERBOSE: Performing the operation "Creating Deployment" on target "alsehrStorageTest-Rg".
VERBOSE: 21:43:43 - Template is valid.
VERBOSE: 21:43:46 - Create template deployment 'main.test'
VERBOSE: 21:43:46 - Checking deployment status in 5 seconds
VERBOSE: 21:43:52 - Resource Microsoft.Storage/storageAccounts 'adpcarmlazsastrg01' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.OperationalInsights/workspaces 'adp-carml-law-strg-01' provisioning status is succeeded
VERBOSE: 21:43:52 - Resource Microsoft.EventHub/namespaces 'adp-carml-evhns-strg-01' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.Resources/deployments 'i4ye4l7ybpx2g-vnet' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.Network/virtualNetworks 'adp-carml-vnet-strg-01' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-v1strg' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.Storage/storageAccounts 'strgazsav1001' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.ManagedIdentity/userAssignedIdentities 'dep-strg-az-msi-x-01' provisioning status is succeeded
VERBOSE: 21:43:52 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-minstrg' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-nfsstrg' provisioning status is running
VERBOSE: 21:43:52 - Resource Microsoft.Storage/storageAccounts 'strgazsax001' provisioning status is running
VERBOSE: 21:43:52 - Checking deployment status in 17 seconds
VERBOSE: 21:44:09 - Resource Microsoft.Resources/deployments 'i4ye4l7ybpx2g-vnet' provisioning status is succeeded
VERBOSE: 21:44:09 - Resource Microsoft.Network/virtualNetworks 'adp-carml-vnet-strg-01' provisioning status is succeeded
VERBOSE: 21:44:09 - Resource Microsoft.Storage/storageAccounts 'strgazsamin001' provisioning status is running
VERBOSE: 21:44:09 - Checking deployment status in 13 seconds
VERBOSE: 21:44:23 - Resource Microsoft.Storage/storageAccounts 'adpcarmlazsastrg01' provisioning status is succeeded
VERBOSE: 21:44:23 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-v1strg' provisioning status is succeeded
VERBOSE: 21:44:23 - Resource Microsoft.Storage/storageAccounts 'strgazsav1001' provisioning status is succeeded
VERBOSE: 21:44:24 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-minstrg' provisioning status is succeeded
VERBOSE: 21:44:24 - Resource Microsoft.Storage/storageAccounts 'strgazsamin001' provisioning status is succeeded
VERBOSE: 21:44:24 - Resource Microsoft.Resources/deployments 'afltjvnan6eey-Storage-FileServices' provisioning status is running
VERBOSE: 21:44:24 - Resource Microsoft.Resources/deployments 'afltjvnan6eey-Storage-FileServices-shares-0' provisioning status is running
VERBOSE: 21:44:24 - Resource Microsoft.Storage/storageAccounts/fileServices 'strgazsax001/default' provisioning status is succeeded
VERBOSE: 21:44:24 - Resource Microsoft.Storage/storageAccounts 'strgazsax001' provisioning status is succeeded
VERBOSE: 21:44:24 - Checking deployment status in 15 seconds
VERBOSE: 21:44:40 - Resource Microsoft.EventHub/namespaces 'adp-carml-evhns-strg-01' provisioning status is succeeded
VERBOSE: 21:44:40 - Resource Microsoft.Resources/deployments 'afltjvnan6eey-Storage-FileServices-shares-0' provisioning status is succeeded
VERBOSE: 21:44:40 - Resource Microsoft.Storage/storageAccounts/fileServices/shares 'strgazsax001/default/nfsfileshare' provisioning status is succeeded
VERBOSE: 21:44:40 - Checking deployment status in 11 seconds
VERBOSE: 21:44:52 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-defstrg' provisioning status is running
VERBOSE: 21:44:52 - Resource Microsoft.Network/virtualNetworks 'adp-carml-vnet-strg-01' provisioning status is succeeded
VERBOSE: 21:44:52 - Resource Microsoft.EventHub/namespaces/authorizationRules 'adp-carml-evhns-strg-01/RootManageSharedAccessKey' provisioning status is succeeded
VERBOSE: 21:44:52 - Resource Microsoft.EventHub/namespaces/eventhubs 'adp-carml-evhns-strg-01/adp-carml-evh-strg-01' provisioning status is succeeded
VERBOSE: 21:44:52 - Checking deployment status in 14 seconds
VERBOSE: 21:45:08 - Resource Microsoft.Storage/storageAccounts 'strgazsax002' provisioning status is running
VERBOSE: 21:45:08 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-nfsstrg' provisioning status is succeeded
VERBOSE: 21:45:08 - Resource Microsoft.Resources/deployments 'afltjvnan6eey-Storage-FileServices' provisioning status is succeeded
VERBOSE: 21:45:08 - Checking deployment status in 11 seconds
VERBOSE: 21:45:24 - Resource Microsoft.Insights/diagnosticSettings 'strgazsax002-diagnosticSettings' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-1' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-table' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices-Container-1' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/blobServices/containers 'strgazsax002/default/archivecontainer' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices-Container-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices-Container-0-Rbac-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/blobServices/containers 'strgazsax002/default/avdscripts' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/blobServices 'strgazsax002/default' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices-shares-1' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/fileServices/shares 'strgazsax002/default/avdprofiles2' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices-shares-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices-shares-0-Rbac-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/fileServices/shares 'strgazsax002/default/avdprofiles' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/fileServices 'strgazsax002/default' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-3' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-file' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-2' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-queue' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-Rbac-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Authorization/roleAssignments '2a5da867-558a-5f19-9662-4f75f13d8375' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-blob' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-TableServices' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Insights/diagnosticSettings 'default-diagnosticSettings' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-TableServices-Table-1' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/tableServices/tables 'strgazsax002/default/table2' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-TableServices-Table-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/tableServices/tables 'strgazsax002/default/table1' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/tableServices 'strgazsax002/default' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Insights/diagnosticSettings 'default-diagnosticSettings' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices-Queue-1' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/queueServices/queues 'strgazsax002/default/queue2' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices-Queue-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices-Queue-0-Rbac-0' provisioning status is running
VERBOSE: 21:45:24 - Resource Microsoft.Authorization/roleAssignments '466d9e24-17c9-5554-9056-3cf85981062b' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/queueServices/queues 'strgazsax002/default/queue1' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts/queueServices 'strgazsax002/default' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts 'strgazsax002' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts 'strgazsax002' provisioning status is succeeded
VERBOSE: 21:45:24 - Resource Microsoft.Storage/storageAccounts 'strgazsax002' provisioning status is succeeded
VERBOSE: 21:45:24 - Checking deployment status in 10 seconds
VERBOSE: 21:45:39 - Resource Microsoft.Insights/diagnosticSettings 'default-diagnosticSettings' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices-Container-1' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices-Container-0-Rbac-0' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Authorization/roleAssignments 'f1583156-5525-5d7c-a200-fe7aefa86744' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Insights/diagnosticSettings 'default-diagnosticSettings' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices-shares-1' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices-shares-0-Rbac-0' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Authorization/roleAssignments '960ca506-c8fb-5a51-9071-375340b72526' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-Rbac-0' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-TableServices-Table-1' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-TableServices-Table-0' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices-Queue-1' provisioning status is succeeded
VERBOSE: 21:45:39 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices-Queue-0-Rbac-0' provisioning status is succeeded
VERBOSE: 21:45:39 - Checking deployment status in 11 seconds
VERBOSE: 21:45:54 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices-Container-0' provisioning status is succeeded
VERBOSE: 21:45:54 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices-shares-0' provisioning status is succeeded
VERBOSE: 21:45:54 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-TableServices' provisioning status is succeeded
VERBOSE: 21:45:54 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices-Queue-0' provisioning status is succeeded
VERBOSE: 21:45:54 - Checking deployment status in 11 seconds
VERBOSE: 21:46:10 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-BlobServices' provisioning status is succeeded
VERBOSE: 21:46:10 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-FileServices' provisioning status is succeeded
VERBOSE: 21:46:10 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-QueueServices' provisioning status is succeeded
VERBOSE: 21:46:10 - Checking deployment status in 11 seconds
VERBOSE: 21:46:26 - Checking deployment status in 10 seconds
VERBOSE: 21:46:41 - Checking deployment status in 11 seconds
VERBOSE: 21:46:57 - Checking deployment status in 11 seconds
VERBOSE: 21:47:13 - Checking deployment status in 10 seconds
VERBOSE: 21:47:29 - Checking deployment status in 10 seconds
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-table/default' provisioning status is running
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-table' provisioning status is succeeded
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-file/default' provisioning status is running
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-file' provisioning status is succeeded
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-queue/default' provisioning status is running
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-queue' provisioning status is succeeded
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-blob/default' provisioning status is running
VERBOSE: 21:47:44 - Resource Microsoft.Network/privateEndpoints 'strgazsax002-blob' provisioning status is succeeded
VERBOSE: 21:47:45 - Checking deployment status in 9 seconds
VERBOSE: 21:47:59 - Resource Microsoft.Resources/deployments 'bku2phqmh3aei-defstrg' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-1' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-table/default' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-3' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-file/default' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-2' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-queue/default' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Resources/deployments 'hlq5asjwnsb3u-Storage-PrivateEndpoints-0' provisioning status is succeeded
VERBOSE: 21:47:59 - Resource Microsoft.Network/privateEndpoints/privateDnsZoneGroups 'strgazsax002-blob/default' provisioning status is succeeded

DeploymentName          : main.test
ResourceGroupName       : test-Rg
ProvisioningState       : Succeeded
Timestamp               : 25.04.2022 19:47:53
Mode                    : Incremental
TemplateLink            :
Parameters              :
                          Name             Type                       Value
                          ===============  =========================  ==========
                          location         String                     "westeurope"
                          serviceShort     String                     "strg"

Outputs                 :
DeploymentDebugLogLevel :

Love the trailblazers...

Closing as the code ran stale (in comparison to CARML latest)

authors: MrMCake bmoore-msft

repo: Azure/bicep-registry-modules


text:
Bicep module to have feature parity with Microsoft.Resources/deployments

I was helping on an issue yesterday and wanted to turn on debugSetting on a nested deployment (I was using a module) and it hit me.
It is very easy and convenient today to use modules, they translate into Microsoft.Resources/deployments. There is no way to set the properties on a Module like it is possible to with Microsoft.Resources/deployments
Describe the solution you'd like
I'd like to be able to control the properties like
    debugSetting: {
      detailLevel: 'string'
    }
    mode: 'string'
    onErrorDeployment: {
      deploymentName: 'string'
      type: 'string'
    }

I know I could declare a deployment resource in Bicep but I loose the transpile and ease that module provides.
I'd like to be able to declare the following in a module:
module keyVault 'keyvault.bicep' = {
  name: 'keyVaultDeployment'
  properties: {
    debugSetting: {
      detailLevel : 'requestContent, responseContent'
    }
    mode: 'complete'
    onErrorDeployment: {
      deploymentName: 'deployment1'
      type: 'SpecificDeployment'
    }
  }
}

Some options probably should not be provided to avoid confusion and encourage usage of upcoming deployment stacks - mode, onErrorDeployment. I believe also some of the settings could not be used on nested templates.

I don't think we want 1:1 parity. As Stan mentioned, there are some capabilities like onErrorDeployment, mode, and the api version we use that we intentionally do not want to expose.
I could potentially see us exposing the debug setting, but would want to discuss that further.

to be honest I have never used the debug settings in real life troubleshooting. They could be useful but in a very rare scenarios for troubleshooting.

Yeah, the need originally was for debugSetting. We could remove the ask for parity here.

To be fair, and aligned with @slavizh's comment. We can ask if people want this.
If not, I'll continue switching the value in a ARM template that I reference as the module source.

@jikuja -- this looks like a slightly different issue. The second error was caught during preflight validation. It didn't manifest in the more complex deployment because the preflight evaluation has a tendency to short-circuit with a particular usage pattern with modules.
Changing the debug setting would allow you to inspect the details of the request, but won't change the error message itself.

Changing the debug setting would allow you to inspect the details of the request, but won't change the error message itself.

True. Updated my message.
But does not change the facts that:

debug level is not inherited into nested templates
response gave answer

This was the erroring deployment result on Portal:

Response was in this case much more better that Status message. I might try this later:

build to JSON
inject debuglevel for all nested template
check if same error and response are present

check if same error and response are present

My assumption is the error will be the same both with and without the debug setting. In the second case, the template didn't pass validation and the RP handles it and gives a helpful error message. In the earlier case, the validation error was missed (not related to debug settings), which apparently results in an Internal Server Error (which is a bug in the resource provider service).

authors: alex-frankel jikuja slapointe slavizh

repo: Azure/bicep


text:
Feedback request - Composite isMobile flag

What
We're looking to add a flag for isMobile in the composites. Looking for feedback on what that API should look like
Why
We are going to give composites a mobile-first view. For desktop we will be setting and documenting a min-height and width that gives an optimal experience (through customer asks we can then put in work to make this smaller and smaller). But mobile will have things like touch targets and UI elements that are optimized for mobile.
Questions

Is this the right place to put this flag?
Is it OK that it defaults to false (opt-in when everything else is opt-out)

Closing this as this was for feedback on API design - implementation will follow shortly

repo: Azure/communication-ui-library


text:
Permission denied inside counterfit Docker container

Problem while creating a new target inside a counterfit docker container:
 [!] Failed to write target file: [Errno 13] Permission denied: 'counterfit/targets/dummy'.
My container is based on the image pulled using docker pull azuretrustworthyml/counterfit:0.1

Any help to fix this please..

Thank you for this! We're investigating.

authors: RamvigneshPasupathy moohax

repo: Azure/counterfit


text:
Add the different kinds of collations for supported types to testing

We currently support types that have potentially different kinds of collations, but these different collations are not included in our tests. Add in support for testing these different collation types.
More information about collation support in SQL can be found here https://learn.microsoft.com/en-us/sql/relational-databases/collations/collation-and-unicode-support?view=sql-server-ver16

@aaronburtle, can you add some example test cases for this to get a better idea of what the missing test coverage is?

authors: aaronburtle seantleonard

repo: Azure/data-api-builder


text:
add Armadillo-IoT GW A6 DoorsMonitor's model v2

Company Info
Atmark Techno, Inc.
https://www.atmark-techno.com/
IoT Plug and Play Device Info
Armadillo-IoT GW A6 doors monitor configuration
https://armadillo.atmark-techno.com/armadillo-iot-a6
Model Submission Goals
Device certification
Code Owners & Reserved Names

Would you merge approved changes?

repo: Azure/iot-plugandplay-models


text:
After migrating to version 1.0.0 - Error encountered while running the test case: 'Cannot find module 'react-azure-maps' from 'src/map/Componentx.tsx'.

What can be the reason for this error after react-azure-maps version update? [from 0.1.4 to 1.0.0]
Cannot find module 'react-azure-maps' from 'src/map/Componentx.tsx'

"dependencies": {
    "@babel/runtime": "^7.17.8",
    "@ericblade/quagga2": "^1.6.0",
    "@google/markerclustererplus": "^4.0.1",
    "@material-ui/core": "^4.9.5",
    "@material-ui/icons": "^4.9.1",
    "@material-ui/lab": "^4.0.0-alpha.46",
    "@microsoft/applicationinsights-web": "^2.2.4",
    "@reduxjs/toolkit": "^1.7.2",
    "@types/enzyme": "^3.10.11",
    "@types/jest": "^27.4.1",
    "@types/lodash": "^4.14.199",
    "@types/node": "^17.0.22",
    "@types/react": "^17.0.41",
    "@types/react-dom": "^17.0.14",
    "@types/react-virtualized": "^9.21.11",
    "@types/styled-components": "^5.1.3",
    "@zxing/library": "0.15.2",
    "autosuggest-highlight": "^3.1.1",
    "axios": "^0.26.1",
    "azure-maps-control": "^3.0.1",
    "azure-maps-indoor": "^0.2.2",
    "azure-maps-rest": "^2.0.5",
    "body-scroll-lock": "^2.6.1",
    "classnames": "^2.3.1",
    "connected-react-router": "^6.7.0",
    "core-js": "^3.6.4",
    "env-cmd": "^10.1.0",
    "es6-shim": "^0.35.3",
    "focus-visible": "^5.2.0",
    "formik": "2.2.9",
    "fstream": "1.0.12",
    "geolib": "^3.3.1",
    "google-maps-react": "^2.0.2",
    "guid-typescript": "^1.0.9",
    "is_js": "^0.9.0",
    "js-cookie": "^2.2.0",
    "js-hash-code": "^1.0.0",
    "json2csv": "^4.2.1",
    "jsonpath": "^1.0.2",
    "jsts": "^2.1.0",
    "lodash": "^4.17.15",
    "merge-prop-functions": "^1.1.0",
    "moment": "^2.22.2",
    "moment-timezone": "^0.5.26",
    "oidc-client": "^1.11.5",
    "papaparse": "^5.1.1",
    "pondjs": "^0.9.0",
    "promise-throttle": "^1.0.0",
    "prop-types": "^15.6.2",
    "qs": "^6.5.2",
    "react": "17.0.2",
    "react-app-rewired": "2.1.5",
    "react-autosuggest": "^9.3.4",
    "react-azure-maps": "^1.0.0",
    "react-csv": "^1.0.14",
    "react-datepicker": "^2.14.0",
    "react-device-detect": "^1.6.2",
    "react-dom": "17.0.2",
    "react-dropzone": "^10.2.1",
    "react-error-boundary": "^3.1.1",
    "react-focus-lock": "^2.9.4",
    "react-format-text": "^1.1.1",
    "react-geolocated": "^3.0.1",
    "react-horizontal-scrolling-menu": "^2.7.1",
    "react-idle-timer": "^4.5.6",
    "react-infinite-scroll-component": "^5.0.5",
    "react-inlinesvg": "^1.2.0",
    "react-loading": "^2.0.3",
    "react-loading-overlay": "^1.0.1",
    "react-loading-skeleton": "^2.0.1",
    "react-redux": "^7.2.0",
    "react-render-html": "^0.6.0",
    "react-resizable": "^1.10.1",
    "react-router-dom": "5.1.2",
    "react-router-navigation-prompt": "^1.8.7",
    "react-scripts": "5.0.0",
    "react-select": "^3.0.8",
    "react-spinkit": "^3.0.0",
    "react-swipe-component": "^3.0.0",
    "react-table": "^6.8.0",
    "react-timeseries-charts": "^0.16.1",
    "react-virtualized": "^9.21.0",
    "redux": "^4.0.0",
    "redux-promise-middleware": "^6.1.2",
    "redux-saga": "^1.1.3",
    "redux-saga-callback": "^1.1.0",
    "redux-thunk": "^2.3.0",
    "reselect": "^4.0.0",
    "sass": "^1.49.9",
    "short-hash": "^1.0.0",
    "styled-components": "^5.0.1",
    "universal-cookie": "^4.0.3",
    "util": "^0.12.4",
    "uuid": "^3.3.2",
    "wellknown": "0.5.0",
    "why-did-you-update": "^1.0.6",
    "yup": "^0.32.11"
  },

devDependencies": {
    "@babel/plugin-transform-runtime": "^7.17.0",
    "@testing-library/react-hooks": "^8.0.1",
    "@types/classnames": "^2.3.1",
    "@types/jsonpath": "^0.2.0",
    "@types/material-ui": "^0.21.9",
    "@types/react-csv": "^1.1.2",
    "@types/react-redux": "^7.1.9",
    "@types/react-router-dom": "^5.1.7",
    "@types/redux-mock-store": "^1.0.2",
    "@wojtekmaj/enzyme-adapter-react-17": "^0.6.6",
    "axios-mock-adapter": "^1.15.0",
    "crypto": "^1.0.1",
    "enzyme": "^3.11.0",
    "enzyme-redux": "^0.2.1",
    "eslint-plugin-prettier": "^4.0.0",
    "jest-canvas-mock": "2.5.0",
    "jest-junit-reporter": "^1.1.0",
    "jest-localstorage-mock": "^2.3.0",
    "prettier": "2.6.0",
    "react-app": "^1.1.2",
    "redux-devtools-extension": "^2.13.8",
    "redux-mock-store": "^1.5.3",
    "redux-saga-test-plan": "^4.0.0-rc.3",
    "sinon": "^9.0.0",
    "ts-jest": "^27.1.3",
    "typescript": "^3.9.6"
  },

Known issue, see https://github.com/Azure/react-azure-maps/issues/102 for details.

repo: Azure/react-azure-maps


text:
secrets-store-csi-driver results in forbidden errors when deployed via Azure ARC onto a K3S cluster

Have you

[x] Read Troubleshooting Guide
[x] Searched on GitHub issues and Discussions

What steps did you take and what happened:

Create a new VM with k3s cluster running)
Onboarding k3s within VM as Arc-enabled cluster
Add extension via azure portal (akvsecretsprovider) / add extension via biscep
Arc monitoring pods for akvsecretsprovider are down, also secret sync does not function. Snippet:azureuser@device-1:~$ kubectl logs -n kube-system arc-monitoring-85d99f94d5-dvmsr fluentd
#<Thread:0x0000564491f875d8 /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluent-plugin-kubernetes_metadata_filter-2.5.3/lib/fluent/plugin/filter_kubernetes_metadata.rb:254 run> terminated with exception (report_on_exception is true):
/opt/td-agent/lib/ruby/gems/2.7.0/gems/fluent-plugin-kubernetes_metadata_filter-2.5.3/lib/fluent/plugin/kubernetes_metadata_watch_namespaces.rb:86:in `rescue in start_namespace_watch': start_namespace_watch:
Exception encountered setting up namespace watch from Kubernetes API v1 endpoint https://10.43.0.1:443/api: namespaces is forbidden: User "system:serviceaccount:kube-system:csi-secrets-store-provider-azure" cannot list resource "namespaces" in API group "" at the cluster scope ({"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"namespaces is forbidden: User \\"system:serviceaccount:kube-system:csi-secrets-store-provider-azure\\" cannot list resource \\"namespaces\\" in API group \\"\\" at the cluster scope","reason":"Forbidden","details":{"kind":"namespaces"},"code":403} (Fluent::ConfigError)

What did you expect to happen:
Secret Storage to work as expected on ARC connected K3S cluster. If there is a better place to post this issue, please let us know :)
Anything else you would like to add:
The bicep template used for deployment, where you can see that the syncSecret is enabled. I've also verified its enabled through the Azure Arc UI in Azure portal:
resource extension 'Microsoft.KubernetesConfiguration/extensions@2021-09-01' = {
  name: 'akvsecretsprovider'
  scope: cluster
  properties: {
    extensionType: 'Microsoft.AzureKeyVaultSecretsProvider'
    releaseTrain: 'stable'
    version: '1.1.3'
    configurationSettings: {
      enableSecretRotation: 'true'
      rotationPollInterval: '2m'
      'syncSecret.enabled': 'true'
    }
  }
}

Here are all of the logs in no particular order: https://gist.github.com/EliiseS/dab2821dd860e9e0402e7843b71dae82
One key takeaway for me has been that the cluster roles are missing, which is most likely the reason the service account is forbidden from doing anything.
Which access mode did you use to access the Azure Key Vault instance:
[e.g. Service Principal, Pod Identity, User Assigned Managed Identity, System Assigned Managed Identity]
Environment:

Secrets Store CSI Driver version: (use the image tag): v2.5.0
Azure Key Vault provider version: (use the image tag): 1.1.3
Kubernetes version: (use kubectl version and kubectl get nodes -o wide):

$ kubectl version
.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3+k3s1", GitCommit:"990ba0e88c90f8ed8b50e0ccd375937b841b176e", GitTreeState:"clean", BuildDate:"2022-07-19T01:10:03Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}

$ kubectl get nodes -o wide
NAME       STATUS   ROLES                  AGE    VERSION        INTERNAL-IP    EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
device-1   Ready    control-plane,master   4d3h   v1.24.3+k3s1   172.16.128.4   <none>        Ubuntu 18.04.6 LTS   5.4.0-1086-azure   containerd://1.6.6-k3s1

Cluster type: (e.g. AKS, aks-engine, etc): K3S
Installation method:  Use Azure Key Vault Secrets Provider extension to fetch secrets into Azure Arc-enabled Kubernetes clusters - Azure Arc | Microsoft Docs
https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/tutorial-akv-secrets-provider

Co-author: @LeonardHd

@EliiseS Thanks for opening issue. As you mentioned the problem is with missing Roles and Role Bindings. Sync secrets and monitoring needs them to work correctly. Could you try installing them manually?
I am looking into possibility that this maybe RBAC issue specific to k3s.

@nilekhc I did some research on the issue, and I hope this helps to further pinpoint the issue.
I suspect that the helm chart does not install the rolebindings based on the conditions in the charts/csi-secrets-store-provider-azure/templates/rolebinding.yaml given that for Values.Azure.Identity.isEnabled the arc-values.yaml is currently set to false.
I am not sure how I could modify that parameter when I deploy the extension for Arc via ARM.
What I did to come to that conclusion:

Clone this repo and apply the helm chart with  Values.Azure.Identity.isEnabled set to true.
Changed arc-monitoring deployment so that higher fluentd resource limits prevent OOMErrors.

Result:

The fluent container does not return the same error.
2022-08-01 14:29:13 +0000 [warn]: #0 failed to flush the buffer. retry_time=0 next_retry_seconds=2022-08-01 14:29:14.773655808 +0000 chunk="5e52ecb83d33d72c8c65769d35902a62" error_class=RuntimeError error="Sending data (tag=akvssd.secrets-store) to mdsd failed"
2022-08-01 14:29:13 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluent-plugin-mdsd-0.1.9.pre.build.dev/lib/fluent/plugin/out_mdsd.rb:108:in `handle_record'
2022-08-01 14:29:13 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluent-plugin-mdsd-0.1.9.pre.build.dev/lib/fluent/plugin/out_mdsd.rb:88:in `block in write'
2022-08-01T14:29:13.7741560Z: error SocketClient.cc:137 Connect() SocketException: SocketClient connect(): No such file or directory
2022-08-01T14:29:13.8955320Z: error SocketClient.cc:137 Connect() SocketException: SocketClient connect(): No such file or directory
2022-08-01T14:29:14.0838950Z: error SocketClient.cc:137 Connect() SocketException: SocketClient connect(): No such file or directory
2022-08-01T14:29:14.4874100Z: error SocketClient.cc:137 Connect() SocketException: SocketClient connect(): No such file or directory
2022-08-01T14:29:15.4202530Z: error SocketClient.cc:137 Connect() SocketException: SocketClient connect(): No such file or directory
2022-08-01T14:29:16.6483850Z: error SocketClient.cc:137 Connect() SocketException: SocketClient connect(): No such file or directory

The prom-mdm-converter is now failing with:
{"fileName":"/Users/nilekh/repos/prom-mdm-converter/cmd/converter.go","level":"fatal","lineNumber":63,"msg":"Required variables not set","serviceBuild":"","source":"AcsContextlessTraceLog","time":"2022-08-01T14:27:40Z"}

For the prom-mdm-convert the issue seems to be the missing Values.Azure.Extension.ResourceId due to my local reproduction of the issue.

@LeonardHd You are certainly debugging in right direction. Let me give you some context.
When we release new Arc extension version, we replace arc-values.yaml into values.yaml to get arc specific configuration and then packs the helm chart. Having said that, Values.Azure section is populated by Arc extension Resource Provider when you install Arc extension. So for extension to work properly (or test properly) you must install it via cli/portal/arm template and not manually via helm chart. Arc should set Values.Azure.Identity.isEnabled to true. You can check values set for Values.Azure using helm get values <RELEASE_NAME>.
Also, I see that you are pinning extension version to 1.1.3. There is newer version 1.2.1 available. I would recommend not to specify version in your Arm template while installing. When version is not specified Arc picks the latest version available and also auto upgrades if any new minor version update is available. You can also remove releaseTrain from template as it's defaulted to stable.

Here is sample output of helm get values after installing extension.
~ $ helm get values -n kube-system sscsi
USER-SUPPLIED VALUES:
Azure:
  Cluster:
    Cloud: AZUREPUBLICCLOUD
    Distribution: kind
    Infrastructure: generic
    Region: eastus2euap
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/akv-arc/providers/Microsoft.Kubernetes/ConnectedClusters/ext-test
  Extension:
    Name: sscsi
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/akv-arc/providers/Microsoft.Kubernetes/ConnectedClusters/ext-test/providers/Microsoft.KubernetesConfiguration/extensions/sscsi
  Identity:
    MSIAdapterYaml: |
      <REDACTED>
    Type: SystemAssigned
    isEnabled: true
  proxySettings:
    isCustomCert: false
    isProxyEnabled: false
IdentityPrincipalId: <REDACTED>
IdentityType: SystemAssigned
scope: cluster
secrets-store-csi-driver:
  enableSecretRotation: true
  rotationPollInterval: 30s
  syncSecret:
    enabled: true

@nilekhc I have installed the extension as follows (on a new Arc-enabled k3s cluster just to be sure 🤓). I kept the version and namespace pinned for now - thanks a lot for the recommendation to not pin it / omit the release train.
helm get values returns the output as below. It seems that Values.Azure.Identity.isEnabled is false, which causes the rolebindings not to be created.
azureuser@device-1:~$ helm get values akvsecretsprovider -n kube-system
USER-SUPPLIED VALUES:
Azure:
  Cluster:
    Cloud: AZUREPUBLICCLOUD
    Distribution: k3s
    Infrastructure: generic
    Region: westeurope
    ResourceId: /subscriptions/<omitted>/resourceGroups/aksplhf-poc-rg/providers/Microsoft.Kubernetes/ConnectedClusters/device-1
  Extension:
    Name: akvsecretsprovider
    ResourceId: /subscriptions/<omitted>/resourceGroups/aksplhf-poc-rg/providers/Microsoft.Kubernetes/ConnectedClusters/device-1/providers/Microsoft.KubernetesConfiguration/extensions/akvsecretsprovider
  Identity:
    isEnabled: false
  proxySettings:
    isCustomCert: false
    isProxyEnabled: false
enableSecretRotation: true
rotationPollInterval: 2m
scope: cluster
syncSecret:
  enabled: true

I used the following bicep:
param clusterName string

resource cluster 'Microsoft.Kubernetes/connectedClusters@2022-05-01-preview' existing = {
  name: clusterName
}

resource extension 'Microsoft.KubernetesConfiguration/extensions@2021-09-01' = {
  name: 'akvsecretsprovider'
  scope: cluster
  properties: {
    extensionType: 'Microsoft.AzureKeyVaultSecretsProvider'
    releaseTrain: 'stable'
    version: '1.2.1'
    scope: {
      cluster: {
        releaseNamespace: 'kube-system'
      }
    }
    configurationSettings: {
      enableSecretRotation: 'true'
      rotationPollInterval: '2m'
      'syncSecret.enabled': 'true'
    }
  }
}

@LeonardHd Could you provide me an output of kubectl get pods -n azure-arc

Sure, no problem:
azureuser@device-1:~$ kubectl get pods -n azure-arc
NAME                                         READY   STATUS    RESTARTS   AGE
flux-logs-agent-68bc745586-2tcx4             1/1     Running   0          23m
cluster-metadata-operator-855c68dcf8-jdrnr   2/2     Running   0          23m
extension-manager-54559794d6-p5bjw           2/2     Running   0          23m
clusteridentityoperator-bd4f4f4c6-288wh      2/2     Running   0          23m
controller-manager-7fcbd6585d-r7chw          2/2     Running   0          23m
metrics-agent-7d6844cd4c-wjp9n               2/2     Running   0          23m
resource-sync-agent-5d755f9d6f-2wtqx         2/2     Running   0          23m
clusterconnect-agent-77496f7c5c-4hn22        3/3     Running   0          23m
config-agent-6f776c77b9-9g9v5                2/2     Running   0          23m
kube-aad-proxy-6cdcc5c95d-wdk54              2/2     Running   0          23m

Thanks for providing an access to your test env @LeonardHd. I tried it out and it works as expected. Here are some of the outputs.
~$ az connectedk8s connect -n k3s-test -g arc-ext
This operation might take a while...

Downloading helm client for first time. This can take few minutes...

{
  "agentPublicKeyCertificate": "<REDACTED>",
  "agentVersion": null,
  "connectivityStatus": "Connecting",
  "distribution": "k3s",
  "id": "/subscriptions/<REDACTED>/resourceGroups/arc-ext/providers/Microsoft.Kubernetes/connectedClusters/k3s-test",
  "identity": {
    "principalId": "<REDACTED>",
    "tenantId": "<REDACTED>",
    "type": "SystemAssigned"
  },
  "infrastructure": "generic",
  "kubernetesVersion": null,
  "lastConnectivityTime": null,
  "location": "eastus2euap",
  "managedIdentityCertificateExpirationTime": null,
  "name": "k3s-test",
  "offering": null,
  "provisioningState": "Succeeded",
  "resourceGroup": "arc-ext",
  "systemData": {
    "createdAt": "2022-08-01T22:17:13.260943+00:00",
    "createdBy": "<REDACTED>",
    "createdByType": "User",
    "lastModifiedAt": "2022-08-01T22:17:13.260943+00:00",
    "lastModifiedBy": "<REDACTED>",
    "lastModifiedByType": "User"
  },
  "tags": {},
  "totalCoreCount": null,
  "totalNodeCount": null,
  "type": "microsoft.kubernetes/connectedclusters"
}

~$ az k8s-extension create \
        --name k3stest \
       --extension-type Microsoft.AzureKeyVaultSecretsProvider \
       --scope cluster \
       --cluster-name k3s-test \
       --resource-group arc-ext \
       --cluster-type connectedClusters \
       --release-namespace kube-system \
       --configuration-settings 'secrets-store-csi-driver.enableSecretRotation=true' \
         'secrets-store-csi-driver.rotationPollInterval=30s' \
         'secrets-store-csi-driver.syncSecret.enabled=true'
{
  "aksAssignedIdentity": null,
  "autoUpgradeMinorVersion": true,
  "configurationProtectedSettings": {},
  "configurationSettings": {
    "secrets-store-csi-driver.enableSecretRotation": "true",
    "secrets-store-csi-driver.rotationPollInterval": "30s",
    "secrets-store-csi-driver.syncSecret.enabled": "true"
  },
  "customLocationSettings": null,
  "errorInfo": null,
  "extensionType": "microsoft.azurekeyvaultsecretsprovider",
  "id": "/subscriptions/<REDACTED>/resourceGroups/arc-ext/providers/Microsoft.Kubernetes/connectedClusters/k3s-test/providers/Microsoft.KubernetesConfiguration/ex
tensions/k3stest",
  "identity": {
    "principalId": "<REDACTED>",
    "tenantId": null,
    "type": "SystemAssigned"
  },
  "name": "k3stest",
  "packageUri": null,
  "provisioningState": "Succeeded",
  "releaseTrain": "Stable",
  "resourceGroup": "arc-ext",
  "scope": {
    "cluster": {
      "releaseNamespace": "kube-system"
    },
    "namespace": null
  },
  "statuses": [],
  "systemData": {
    "createdAt": "2022-08-01T22:25:02.943164+00:00",
    "createdBy": null,
    "createdByType": null,
    "lastModifiedAt": "2022-08-01T22:25:02.943164+00:00",
    "lastModifiedBy": null,
    "lastModifiedByType": null
  },
  "type": "Microsoft.KubernetesConfiguration/extensions",
  "version": "1.2.1"
}

Output of helm get values k3stest -n kube-system does show that Identity.isEnabled is set to true
Azure:
  Cluster:
    Cloud: AZUREPUBLICCLOUD
    Distribution: k3s
    Infrastructure: generic
    Region: eastus2euap
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/arc-ext/providers/Microsoft.Kubernetes/ConnectedClusters/k3s-test
  Extension:
    Name: k3stest
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/arc-ext/providers/Microsoft.Kubernetes/ConnectedClusters/k3s-test/providers/Microsoft.KubernetesConfigura
tion/extensions/k3stest
  Identity:
    Type: SystemAssigned
    isEnabled: true
  proxySettings:
    isCustomCert: false
    isProxyEnabled: false
IdentityPrincipalId: <REDACTED>
IdentityType: SystemAssigned
scope: cluster
secrets-store-csi-driver:
  enableSecretRotation: true
  rotationPollInterval: 30s
  syncSecret:
    enabled: true

After creating workload pod it was able to mount secret on the volume.
~$ kubectl exec -it busybox-secrets-store-inline -- cat /mnt/secrets-store/secret1
testazureuser

@nilekhc I have managed to dig further, and I believe I have found the issue.
Possible findings in short

Azure Portal extension deployment arc/portal_gallery_package/DeploymentTemplates/DefaultTemplate.json for Azure Arc-enabled clusters is missing an identity of type SystemAssigned. Causing missing rolebindings on the target cluster.
Microsoft docs: Missing identity in the docs' ARM template (Use the Azure Key Vault Secrets Provider extension to fetch secrets into Azure Arc-enabled Kubernetes clusters).

Details
Installing via the az CLI indeed works as expected, however, the issue persisted deploying the extension via the Azure Portal and ARM/Bicep.
In fact, when deploying via the Arc Extension Tab the Values.Azure.Identity.isEnabled is false (see Azure Portal Deployment Helm Values below). This currently does not cause an error in the installation process.

The difference I noticed between CLI and Portal/ARM is that the az CLI creates always an identity (as of your output; and I also tracked down the corresponding code in the az cli here (DefaultExtension.py line 52).
This made me add a SystemAssigned identity to my bicep template (see Bicep template below), and this seems to resolve the issue with Values.Azure.Identity.isEnabled being false. The helm get values also returns a more 'reasonable' output.
ARM/Bicep deployment with SystemAssigned identity
param clusterName string

resource cluster 'Microsoft.Kubernetes/connectedClusters@2022-05-01-preview' existing = {
  name: clusterName
}

resource extension 'Microsoft.KubernetesConfiguration/extensions@2021-09-01' = {
  name: 'akvsecretsprovider'
  scope: cluster
  identity: {
    type: 'SystemAssigned'
  }
  properties: {
    extensionType: 'Microsoft.AzureKeyVaultSecretsProvider'
    releaseTrain: 'stable'
    version: '1.2.1'
    scope: {
      cluster: {
        releaseNamespace: 'kube-system'
      }
    }
    configurationSettings: {
      enableSecretRotation: 'true'
      rotationPollInterval: '2m'
      'syncSecret.enabled': 'true'
    }
  }
}

helm get values for ARM/Bicep deployment with SystemAssigned identity
azureuser@device-1:~$ helm get values akvsecretsprovider -n kube-system
USER-SUPPLIED VALUES:
Azure:
  Cluster:
    Cloud: AZUREPUBLICCLOUD
    Distribution: k3s
    Infrastructure: generic
    Region: westeurope
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/aksplhf-poc-rg/providers/Microsoft.Kubernetes/ConnectedClusters/device-1
  Extension:
    Name: akvsecretsprovider
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/aksplhf-poc-rg/providers/Microsoft.Kubernetes/ConnectedClusters/device-1/providers/Microsoft.KubernetesConfiguration/extensions/akvsecretsprovider
  Identity:
    MSIAdapterYaml: |
      - name: EXTENSION_ARMID
        value: /subscriptions/<REDACTED>/resourceGroups/aksplhf-poc-rg/providers/Microsoft.Kubernetes/ConnectedClusters/device-1/providers/Microsoft.KubernetesConfiguration/extensions/akvsecretsprovider
      - name: EXTENSION_NAME
        value: akvsecretsprovider
      - name: CLUSTER_IDENTITY
        value: "false"
      - name: CLUSTER_TYPE
        value: ConnectedClusters
      - name: MANAGED_IDENTITY_AUTH
        value: "true"
      - name: TEST_MODE
        value: "false"
      - name: TEST_FILE
        value: "/data/token"
      image: mcr.microsoft.com/azurearck8s/msi-adapter:1.0.0
      securityContext:
        capabilities:
          add:
            - NET_ADMIN
            - NET_RAW
      livenessProbe:
        httpGet:
          path: /healthz
          port: 9090
          scheme: "HTTP"
        initialDelaySeconds: 10
        periodSeconds: 15
      resources:
        limits:
          cpu: 50m
          memory: 100Mi
        requests:
          cpu: 20m
          memory: 50Mi
    Type: SystemAssigned
    isEnabled: true
  proxySettings:
    isCustomCert: false
    isProxyEnabled: false
IdentityPrincipalId: <REDACTED>
IdentityType: SystemAssigned
enableSecretRotation: true
rotationPollInterval: 2m
scope: cluster
syncSecret:
  enabled: true

Azure Portal ARM Deployment
{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "releaseTrain": {
            "defaultValue": "stable",
            "type": "String"
        },
        "releaseNamespace": {
            "defaultValue": "kube-system",
            "type": "String"
        },
        "extensionName": {
            "defaultValue": "akvsecretsprovider",
            "type": "String"
        },
        "connectedClusterName": {
            "type": "String"
        },
        "enableSecretRotation": {
            "defaultValue": "false",
            "type": "String"
        },
        "rotationPollInterval": {
            "defaultValue": "2m",
            "type": "String"
        },
        "enableSyncSecret": {
            "defaultValue": "false",
            "type": "String"
        },
        "tagsByResource": {
            "defaultValue": {},
            "type": "Object"
        }
    },
    "variables": {},
    "functions": [],
    "resources": [
        {
            "type": "Microsoft.KubernetesConfiguration/extensions",
            "apiVersion": "2021-09-01",
            "name": "[parameters('extensionName')]",
            "tags": "[ if(contains(parameters('tagsByResource'), 'Microsoft.KubernetesConfiguration/extensions'), parameters('tagsByResource')['Microsoft.KubernetesConfiguration/extensions'], json('{}')) ]",
            "properties": {
                "extensionType": "Microsoft.AzureKeyVaultSecretsProvider",
                "releaseTrain": "[parameters('releaseTrain')]",
                "scope": {
                    "cluster": {
                        "releaseNamespace": "[parameters('releaseNamespace')]"
                    }
                },
                "configurationSettings": {
                    "secrets-store-csi-driver.enableSecretRotation": "[parameters('enableSecretRotation')]",
                    "secrets-store-csi-driver.rotationPollInterval": "[parameters('rotationPollInterval')]",
                    "secrets-store-csi-driver.syncSecret.enabled": "[parameters('enableSyncSecret')]"
                }
            },
            "scope": "[concat('Microsoft.Kubernetes/connectedClusters/', parameters('connectedClusterName'))]"
        }
    ]
}

Azure Portal Deployment Helm Values:
azureuser@device-1:~$ helm get values akvsecretsprovider -n kube-system
USER-SUPPLIED VALUES:
Azure:
  Cluster:
    Cloud: AZUREPUBLICCLOUD
    Distribution: k3s
    Infrastructure: generic
    Region: westeurope
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/akspport-poc-rg/providers/Microsoft.Kubernetes/ConnectedClusters/device-1
  Extension:
    Name: akvsecretsprovider
    ResourceId: /subscriptions/<REDACTED>/resourceGroups/akspport-poc-rg/providers/Microsoft.Kubernetes/ConnectedClusters/device-1/providers/Microsoft.KubernetesConfiguration/extensions/akvsecretsprovider
  Identity:
    isEnabled: false
  proxySettings:
    isCustomCert: false
    isProxyEnabled: false
scope: cluster
secrets-store-csi-driver:
  enableSecretRotation: true
  rotationPollInterval: 2m
  syncSecret:
    enabled: true

Thanks @LeonardHd for debugging and a PR. I'll review the same

@LeonardHd I have also released these changes in portal.

authors: EliiseS LeonardHd nilekhc


text:
Script.md to index PR for #5

NOTE:  This PR depends on #10 since I had to fix the pre-commit messages for it to work.  Merge conflict might occur.
This is a PR for my proposal of Issue #5.
It was essentially these commands:

Rename files script.md -> README.md
for file in $(git ls-files | grep script.md | sed -e 's/\(script.md[^/]*\).*/\1/' | uniq); git mv $file $(echo $file | sed -e 's/script.md/README.md/')

Refactor code
git grep -lz script.md | xargs -0 sed -i '' -e 's/script.md/README.md/g'

Addition of Environment.get_script_file_name(script_dir)

replace hard-coding of script.md with env.get_script_file_name()

Change any "script.md" conditionals to look for "script.md" or "README.md"

@lastcoolnameleft,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Yup, looks like there's a merge conflict due to #11.  Once that's checked in, I'll resolve.  That said, I'd appreciate a look-over to make sure I'm on the right track.

I've merged #5 so resolving conflicts should now be easy.
I think this is the right approach (I've not tested though). One thought would be to make the README.md option config.default_file. This would allow us to change it in specific environments should that ever become necessary. That said, I don't have a real use case at this point and I'll merge with "README.md" rather than block on this.

I have a PR in the queue (#14) which will have conflicts with this PR. I'd really appreciate a review of #14. It's a cool feature, but quite a significant change to the code.
I'd like to merge this and work soon so that I can resolve the resulting conflicts in #14 in parallel to the review.

@rgardler Conflict resolved.
FYI, I tried adding a "test-legacy" directory which utilized a script.md file to ensure it worked; however, it altered the other test cases too much.  So, I manually tested and it works for me with either README.md or script.md.

authors: lastcoolnameleft msftclas rgardler

repo: Azure/simdem