text:
Getting lots of Task Canceled Exception when using Azure Search .Net SDK to merge or upload documents asynchronously

We are using Azure Search .Net SDK(v3.0.4) to merge or upload documents to one of the azure search index.
We are using the below code for the same:
var batch = IndexBatch.MergeOrUpload(documentList);
await searchIndexClient.Documents.IndexAsync(batch);
We are indexing 2 types of subindexes using the same search client. When there is a high load, we are facing lots of task cancelled exceptions and the operation is failing without any hint to inner exceptions. Can someone help me here why this issue might be there?
Stacktrace for reference: System.Threading.Tasks.TaskCanceledException: A task was canceled. at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Rest.RetryDelegatingHandler.<>c__DisplayClass11_0.d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Rest.RetryDelegatingHandler.d__11.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Net.Http.HttpClient.d__58.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Azure.Search.DocumentsOperations.d__23.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Azure.Search.DocumentsOperationsExtensions.d__13`1.MoveNext() --- End of stack trace from previous location where exception was thrown ---

@SONIA111111 Thanks for reporting this. This looks like a service issue rather than a client issue, so I'm going to close this and follow up with you through other channels.

repo: Azure/azure-sdk-for-net


text:
Release Data Protection Extensions Packages

Summary
Release the data protection extensions packages:

Azure.Extensions.AspNetCore.DataProtection.Keys
Azure.Extensions.AspNetCore.DataProtection.Blobs

References and Related

[ASP.NET Extensions] Data Protection Bump (#33011)
CVE in System.Drawing.Common 4.7.0 dependency (#32781)

These have been released.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Auto rest - .net client that uses current Prod version(2015-01-14-preview) of Intune swagger manifest

Updated API version from 2015-01-14-privatepreview to 2015-01-14-preview

Hi @vrmurthy01, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (vrmurthy). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

source: gharchive/pull-request


text:
Add tests for new Copy/Update-LongTermRetentionBackup

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[x] 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.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

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.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.
If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version,

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

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


text:
[Network] Remove one instrument operation

We need to add virtual keyword for all the get child resource method, but one test in network with the implementation of InstrumentOperation method will fail due to this change, so remove it.
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] 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.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

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.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Just curious, what's InstrumentOperation for?

Just curious, what's InstrumentOperation for?

It's used to create class proxy.


text:
Add PiiEntities to Azure.AI.TextAnalytics

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check for Azure.AI.TextAnalytics
API changes have been detected in Azure.AI.TextAnalytics. You can review API changes here
API changes
+             V2022_03_01_Preview = 4,
-         public TextAnalyticsClientOptions(ServiceVersion version = V3_2_Preview_2);
+         public TextAnalyticsClientOptions(ServiceVersion version = V2022_03_01_Preview);
+         public static TextAnalyticsOperationStatus PartiallySucceeded { get; }

authors: azure-sdk nisha-bhatia


text:
Automanage SDK track 2 generation and tests

Track 2 SDK generation
Tests to cover all main operations of the SDK

/check-enforcer evaluate

/azp run net - automanage - ci

/azp run prepare-pipelines

/azp run net - automanage - ci

Also missing the API / snippets run the following from root of your repo
.\eng\scripts\Export-API.ps1 automanage
.\eng\scripts\Update-Snippets.ps1 automanage

#sign-off

/azp run net - automanage - mgmt - ci

/azp prepare net - automanage - mgmt - ci

/azp run prepare-pipelines

/azp run net - automanage - mgmt - ci

/azp run net - automanage - mgmt


text:
generates sdk based on new proposed v3 spec

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Quota

authors: azure-sdk tejasm-microsoft


text:
ADF Documentation/Example using a Scheduled Trigger?

As always, thanks for this library.
This a azure.mgmt.datafactory question.
This is not necessarily an issue, maybe something that is not clear in the documentation.
Not sure what I'm doing wrong here and unfortunately the documentation is not enough to guide me through the process, or maybe I'm missing something. The below code is how I build all the elements required to create and start a scheduled trigger.
My question is, do you have a simple example of a scheduled trigger creation using the Python SDK?
params_for_pipeline = {}
adf_client = DataFactoryManagementClient(credentials, subscription_id)

pl_resource_object = PipelineResource(activities=[act2,act3,act4],
                                         parameters=params_for_pipeline)

pl_resource = adf_client.pipelines.create_or_update(resource_group_name=rg_name,
                                                            factory_name=df_name,
                                                            pipeline_name=pipeline_name,
                                                            pipeline=pl_resource_object)

# Schedule Runs
pl_reference = PipelineReference(reference_name=pipeline_name)

trigger_pl_reference = TriggerPipelineReference(pl_reference, parameters=params_for_pipeline)
pl_scheduled = [trigger_pl_reference]
str_start_date = '2017-10-31T18:23:00'
str_end_date = '2099-12-31T05:00:00'
start_time = datetime.strptime(str_start_date, "%Y-%m-%dT%H:%M:%S").isoformat()
end_time = datetime.strptime(str_start_date, "%Y-%m-%dT%H:%M:%S").isoformat()

recurrence = ScheduleTriggerRecurrence(frequency='Minute', interval=4,
                                               start_time=start_time,
                                               end_time=end_time,
                                               time_zone='UTC')
schedule_trigger = ScheduleTrigger(pipelines=pl_scheduled, recurrence=recurrence)

adf_client.triggers.create_or_update(resource_group_name=rg_name,
                                            factory_name=df_name,
                                             trigger_name='test',
                                           properties=schedule_trigger)

trigger_start = adf_client.triggers.start(resource_group_name=rg_name, factory_name=df_name, trigger_name='test')

Error message: Caused by ResponseError('too many 500 error responses',)
given the details of the error message is very hard to tell what's going on, however I'm able to run the same pipeline manually using the create_run()
Note: I'm not putting details on linked services and data sets, those are working in the manual run so I'm assuming the problem is in the scheduled trigger implementation.
I'm trying to follow this [documentation] (https://docs.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#scheduler-trigger)

Never mind, I figured this one out, however the errors messages weren't helping :) , for documentation purposes only, the problem is the way I formatted the dates in the recurrence (ScheduleTriggerRecurrence object)
python isoformat() does not include the UTC offset (-08:00, -04:00, etc.)
I had to add the UTC offset and voila!
for example:
        str_start_date = '2017-10-31T17:17:00-04:00'
        str_end_date = '2099-12-31T05:30:00-04:00'

This post also helped me to get there:
https://stackoverflow.com/questions/19654578/python-utc-datetime-objects-iso-format-doesnt-include-z-zulu-or-zero-offset
I'm still curious to see how to use the time_zone argument as I was originally using 'UTC', for now I removed it and hard-coded the UTC offset.

@saulcruz, thank you for reporting we will open internal items to improve our error messaging. @sharonlo101 will follow up with documentation.

@saulcruz By default, Python does not set the tzinfo (too dangerous and not obvious). But if you do it yourself, isoformat will do it:
In [8]: datetime.datetime(2017,10,10,12,45,16,tzinfo=datetime.timezone.utc).isoformat()
Out[8]: '2017-10-10T12:45:16+00:00'

In [10]: datetime.datetime(2017,10,10,12,45,16).isoformat()
Out[10]: '2017-10-10T12:45:16'

Note that the SDK install python-dateutil, which can help as well:
In [11]: from dateutil.tz import tzlocal
In [13]: datetime.datetime(2017,10,10,12,45,16,tzinfo=tzlocal()).isoformat()
Out[13]: '2017-10-10T12:45:16-07:00'

Note that the last one will use the tz of the system. It's nice for a desktop machine, usually more dangerous for a VM or a server.

authors: hvermis lmazuel saulcruz

repo: Azure/azure-sdk-for-python


text:
Task remains active even if the task it depends on fails.

Package Name=azure-batch:
Package Version=12.0.0:
Operating System=ubuntu:
Python Version=3.8:

Describe the bug
Running a job on Azure batch pool, with two tasks A and B that have the dependency: B dependent on A.
A failed; however, B does not fail and is still in status running.
To Reproduce
Steps to reproduce the behavior:

Create a job with two tasks, A and B, Where B dependent on A
Make A to fail with exit code 1

Expected behavior
Task B should fail.
Screenshots

In the screenshot, the task sub_dummy_process has a dependency on failing_dummy_process.
Additional context
Code context
dependencies = azure.batch.TaskDependencies(task_ids=depends_on) task = azure.batch.TaskAddParameter(         id=task_id,         user_identity=user,         required_slots=1,         depends_on=dependancies     ) batch_client.task.add(                 job_id=job_id,                 task=task             )

Hi, @Itamar-Erez-Cognata at the task level, this is by design. If you are looking for a failure signal, you can set the Job's OnTaskFailure option to initiate a terminate Job action instead.


text:
Example using azure-synapse library to create new pipeline run

Is your feature request related to a problem? Please describe.
Documentation does not provide guidance on how to use Python SDK to initiate a pipeline run in Synapse Analytics workspace?
Describe the solution you'd like
Is it possible to provide an example of how Python SDK can be used to initiate a pipeline run in Synapse Analytics workspace?
Describe alternatives you've considered
I've been looking at the code in /main/sdk/synapse/azure-synapse-artifacts/azure/synapse/artifacts/operations/_pipeline_operations.py and /main/sdk/synapse/azure-synapse-artifacts/azure/synapse/artifacts/operations/_pipeline_run_operations.py and it is not clear which will give me the ability to kick off the run/execution of an existing pipeline. It's also not clear how I authenticate and provide the details like the workspace where this pipeline is stored.
Additional context
Customers will appreciate being able to orchestrate Synapse Pipelines via Python SDK.

Thanks for reaching out.
Please check https://gist.github.com/xiangyan99/799b7f9d07a74ea895ae069838ae4410 and let us know if it does not work.

Yes, this can be closed.


text:
Attestation Content Validation Issue for learn.microsoft website

Section link:

https://learn.microsoft.com/en-us/python/api/overview/azure/security-attestation-readme?view=azure-python

Reason:
Link validation issue: Broken crosslink. Links do not match, please upload the correct link.
Right link: https://pypi.org/project/azure-security-attestation/

Section link:

https://learn.microsoft.com/en-us/python/api/overview/azure/security-attestation-readme?view=azure-python#prerequisites

Reason:
Link validation issue: Broken crosslink. Links do not match, please upload the correct link.

Section link:

https://learn.microsoft.com/en-us/python/api/overview/azure/security-attestation-readme?view=azure-python#key-concepts

Reason:
Link validation issue: Broken link. Please upload the correct link.
Right link: https://learn.microsoft.com/en-us/python/api/overview/azure/security-attestation-readme?view=azure-python#attestation-service-token-signing-certificate-discovery-and-validation

Section link:

https://learn.microsoft.com/en-us/python/api/overview/azure/security-attestation-readme?view=azure-python#set-an-attestation-policy-for-a-specified-attestation-type

Reason:
Link validation issue: Broken links. Click to report a 404 error.

Section links:

https://learn.microsoft.com/en-us/python/api/azure-security-attestation/azure.security.attestation.aio.attestationadministrationclient?view=azure-python
https://learn.microsoft.com/en-us/python/api/azure-security-attestation/azure.security.attestation.aio.attestationclient?view=azure-python#azure-security-attestation-aio-attestationclient-attest-open-enclave
https://learn.microsoft.com/en-us/python/api/azure-security-attestation/azure.security.attestation.attestationadministrationclient?view=azure-python#azure-security-attestation-attestationadministrationclient-get-policy-management-certificates
https://learn.microsoft.com/en-us/python/api/azure-security-attestation/azure.security.attestation.attestationclient?view=azure-python#azure-security-attestation-attestationclient-attest-open-enclave

Reason:
Format validation Issue: The code example is not indented correctly.

Section links:

https://learn.microsoft.com/en-us/python/api/azure-security-attestation/azure.security.attestation.aio.attestationadministrationclient?view=azure-python#azure-security-attestation-aio-attestationadministrationclient-reset-policy
https://learn.microsoft.com/en-us/python/api/azure-security-attestation/azure.security.attestation.aio.attestationclient?view=azure-python#azure-security-attestation-aio-attestationclient-attest-sgx-enclave

Reason:
Format validation Issue: Format messy.

Section link1, link2, link3, link4, link5, link6, link7, link8, link9, link10, link11, link12:

Reason:
Format validation Issue: Miss Description.

Section links:

https://learn.microsoft.com/en-us/python/api/azure-mgmt-attestation/azure.mgmt.attestation.aio.operations.attestationprovidersoperations?view=azure-python
https://learn.microsoft.com/en-us/python/api/azure-mgmt-attestation/azure.mgmt.attestation.aio.operations.operations?view=azure-python
https://learn.microsoft.com/en-us/python/api/azure-mgmt-attestation/azure.mgmt.attestation.operations.attestationprovidersoperations?view=azure-python
https://learn.microsoft.com/en-us/python/api/azure-mgmt-attestation/azure.mgmt.attestation.operations.operations?view=azure-python

Reason:
Typing annotation Issue: Please unify the format, update to *args:Any, **kwargs:Any or *args, **kwargs.

@rohit-ganguly , @lmazuel , @LarryOsterman and @anilba06 for notification.

Close this issue as we'll put it into a summarzied one.


text:
Create readme

This tracks the work for generating the readme for the library

closed by https://github.com/Azure/azure-sdk-for-python/pull/9775

authors: AlexGhiondea bryevdv


text:
[AutoPR eventhub/resource-manager] EventHub: 2017-04-01 - Added the missing API

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

Codecov Report

Merging #1939 into restapi_auto_eventhub/resource-manager will decrease coverage by <.01%.
The diff coverage is 53.39%.

@@                            Coverage Diff                             @@
##           restapi_auto_eventhub/resource-manager    #1939      +/-   ##
==========================================================================
- Coverage                                   53.15%   53.15%   -0.01%
==========================================================================
  Files                                        4724     4730       +6
  Lines                                      117181   117283     +102
==========================================================================
+ Hits                                        62293    62347      +54
- Misses                                      54888    54936      +48

Impacted Files
Coverage Δ

azure-mgmt-eventhub/azure/mgmt/eventhub/version.py
100% <100%> (ø)
:arrow_up:

...venthub/azure/mgmt/eventhub/operations/__init__.py
100% <100%> (ø)
:arrow_up:

...mt-eventhub/azure/mgmt/eventhub/models/__init__.py
100% <100%> (ø)
:arrow_up:

...azure/mgmt/eventhub/event_hub_management_client.py
100% <100%> (ø)
:arrow_up:

...ure/mgmt/eventhub/operations/regions_operations.py
37.5% <37.5%> (ø)

...t/eventhub/operations/messaging_plan_operations.py
43.33% <43.33%> (ø)

...nthub/azure/mgmt/eventhub/models/messaging_plan.py
50% <50%> (ø)

...hub/models/premium_messaging_regions_properties.py
62.5% <62.5%> (ø)

.../mgmt/eventhub/models/premium_messaging_regions.py
71.42% <71.42%> (ø)

...eventhub/models/premium_messaging_regions_paged.py
80% <80%> (ø)

... and 6 more

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 1396425...13ee241. Read the comment docs.

authors: AutorestCI codecov-io


text:
[ACS][CallAutomation] Migrate test to use playback tests

Issue: https://github.com/Azure/azure-sdk-for-python/issues/31980
This updates to work with new plyaback test to work with asset uploaded here (https://github.com/Azure/azure-sdk-assets/tree/python/communication/azure-communication-callautomation_238e3f10c9)

Updated to use AzureRecordedTestCase
Deleted custom recordings (i.e. incoming events)
Updated to have custom recordings work with asset repo and its playback
Sanitization added for recordings
Updated to work with better event handling
Overall bug fixes and improvements on usuage

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

authors: azure-sdk minwoolee-msft


text:
[Storage] Update Blob CHANGELOG after hotfix

Normally I would merge the hotfix branch back to main but that has proved problematic in the past and the fix itself was already in main. The only diff needed is the CHANGELOG, so just manually updating that.

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

authors: azure-sdk jalauzon-msft


text:
[AutoPR] cognitiveservices/data-plane/QnAMaker

Created to accumulate context: cognitiveservices/data-plane/QnAMaker

(message created by the CI based on PR content)

Codecov Report

Merging #4951 into master will decrease coverage by 3.97%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4951      +/-   ##
==========================================
- Coverage   52.71%   48.74%   -3.98%
==========================================
  Files       11020     6603    -4417
  Lines      230773   184910   -45863
==========================================
- Hits       121660    90137   -31523
+ Misses     109113    94773   -14340

Impacted Files
Coverage Δ

...afactory/azure/mgmt/datafactory/models/__init__.py
50.67% <0%> (-49.33%)
:arrow_down:

...ights/azure/applicationinsights/models/__init__.py
51% <0%> (-49%)
:arrow_down:

...e/cognitiveservices/vision/face/models/__init__.py
51.08% <0%> (-48.92%)
:arrow_down:

...services/language/textanalytics/models/__init__.py
51.16% <0%> (-48.84%)
:arrow_down:

...iveservices/search/entitysearch/models/__init__.py
51.25% <0%> (-48.75%)
:arrow_down:

azure-eventgrid/azure/eventgrid/models/__init__.py
51.25% <0%> (-48.75%)
:arrow_down:

...ration/azure/mgmt/datamigration/models/__init__.py
51.27% <0%> (-48.73%)
:arrow_down:

...ure/mgmt/recoveryservicesbackup/models/__init__.py
51.46% <0%> (-48.54%)
:arrow_down:

...ce/azure/mgmt/containerinstance/models/__init__.py
51.8% <0%> (-48.2%)
:arrow_down:

...tiveservices/search/videosearch/models/__init__.py
52.08% <0%> (-47.92%)
:arrow_down:

... and 4503 more

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 21fda3c...a53f17b. Read the comment docs.


text:
[AutoPR] datamigration/resource-manager

Created to accumulate context: datamigration/resource-manager

(message created by the CI based on PR content)


text:
[AutoPR resources/resource-manager] Swagger specifications for 2019-10-01 Tags API for resources and subscriptions

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

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


text:
Use breadcrumbfiles associated with each asset, versus shared

See title. This addresses the issues that were temporarily mitigated by this .NET PR.

Is this going to have any conflicts when people upgrade locally? i.e. if the new proxy ignores the existing old breadcrumb file, will it try to overwrite stuff or use different paths? I don't fully understand the "pre-breadcrumb file" behavior.

Is this going to have any conflicts when people upgrade locally? i.e. if the new proxy ignores the existing old breadcrumb file, will it try to overwrite stuff or use different paths? I don't fully understand the "pre-breadcrumb file" behavior.

It'll write new ones now. Should be seamless upgrade.

/azp run tools - test-proxy - tests

/apz run tools - test-proxy - tests

Is this going to have any conflicts when people upgrade locally? i.e. if the new proxy ignores the existing old breadcrumb file, will it try to overwrite stuff or use different paths? I don't fully understand the "pre-breadcrumb file" behavior.

It'll write new ones now. Should be seamless upgrade.

However, thinking about this over the afternoon, this upgrade will require an update of the transition script + documentation. My current plan is to

Get this tested and entirely green and merged.
In the same PR that I bump the version of the proxy in, I'll also update the migration script resources under eng/common/testproxy/transition-script/. We were also asking that I move it under onboarding as well. I may as well knock out all of that at the same time while I touch the script.

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests

No commit pushedDate could be found for PR 6604 in repo Azure/azure-sdk-tools

What does this even mean devops bot!?

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests

authors: benbp scbedd

repo: Azure/azure-sdk-tools


text:
Cannot send dependency to Configure that depends on IHubContext

An error is thrown when passing a custom service to the Configure method of the Startup class when using AddAzureSignalR service. This is in ASP.NET Core 2.1. My code:
public interface IDatabaseChangeNotificationService
    {
        void Config();
    }

public class SqlDependencyService : IDatabaseChangeNotificationService
{
public SqlDependencyService( IHubContext<ChatHub> chatHub)
        {
        }

        public void Config()
        {
        }
}

// in the ConfigureServices method:

services.AddScoped<IDatabaseChangeNotificationService, SqlDependencyService>();

            services.AddSignalR().AddAzureSignalR("My Secret key");

// Configure method:

public void Configure(IApplicationBuilder app,
            IHostingEnvironment env,
            IDatabaseChangeNotificationService notificationService)
 {
if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }
            else
            {
                app.UseExceptionHandler("/Home/Error");
                app.UseHsts();
            }

            app.UseHttpsRedirection();
            app.UseStaticFiles();
            app.UseCookiePolicy();

            app.UseAzureSignalR(x =>
            {
                x.MapHub<ChatHub>("/chatHub");
            });

            app.UseMvc(routes =>
            {
                routes.MapRoute(
                    name: "default",
                    template: "{controller=Home}/{action=Index}/{id?}");
            });

            notificationService.Config();
}

Where ChatHub is a class the inherits from Hub (no constructor on this class). If I run the app, I get the following error:

System.InvalidOperationException: 'AddAzureSignalR(...)' was called without a matching call to 'IApplicationBuilder.UseAzureSignalR(...)'.
at Microsoft.Azure.SignalR.ServiceLifetimeManager1..ctor(IServiceConnectionManager1 serviceConnectionManager, IClientConnectionManager clientConnectionManager, IHubProtocolResolver protocolResolver, ILogger1 logger, AzureSignalRMarkerService marker) --- End of stack trace from previous location where exception was thrown ---    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitSingleton(SingletonCallSite singletonCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitSingleton(SingletonCallSite singletonCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.b__0(ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
at Microsoft.AspNetCore.Hosting.Internal.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder)

The issue goes away if I remove the IHubContext dependency from the SqlDependencyService class, or if I remove the use of the functions AddAzureSignalR and UseAzureSignalR.

We will check whether UseAzureSignalR is called in methods of HubLifetimeManager instead of constructor.

@xscript That would be much cleaner. We do a similar thing in redis (https://github.com/aspnet/SignalR/blob/adc5706bcb2b3cb85e98e303999eb9a778426f7c/src/Microsoft.AspNetCore.SignalR.Redis/RedisHubLifetimeManager.cs#L490)

We've been struck by this issue as well. We need to perform some calls as part of the startup of our service after the IoC container was set up, but before the webhost has been started (by building the webhost, creating service scope, and resolving the required services from it). Somewhere down the line, a singleton is required which in turn requires an IHubContext<>. This is merely injected though and no operation is performed with it during the startup process.
The singleton cannot be instantiated however because of this exception. We've worked around it by creating a new class implementing the same interface as the singleton, registering the singleton as its own type (instead of its interface), and have the wrapper class use a Lazy<Singleton> instead. It works, but we would really like to see this exception gone.

OK guys I am also stuck with the same issue
Here is my configure code
public void ConfigureServices(IServiceCollection services)
{
services.Configure(Configuration.GetSection("Dx1Configuration"));
services.Configure(Configuration.GetSection("Authentication:IdentityServer"));
services.AddScoped();
services.AddScoped();
        //Configure SnapshotCollector from application settings
        services.Configure<SnapshotCollectorConfiguration>(Configuration.GetSection(nameof(SnapshotCollectorConfiguration)));

        //Add SnapshotCollector telemetry processor.
        services.AddSingleton<ITelemetryProcessorFactory>(sp => new SnapshotCollectorTelemetryProcessorFactory(sp));

        DxServiceProvider.SetLogger(
            new DxServerLogger(
                Configuration["Dx1Configuration:AppInsightsFilter:InstrumentationKey"],
                Configuration["Dx1Configuration:AppInsightsFilter:AppName"],
                bool.Parse(Configuration["Dx1Configuration:AppInsightsFilter:EnableTracing"])));

        services.AddSingleton(_ => Configuration);

        //Configure response compression
        services.Configure<GzipCompressionProviderOptions>(options =>
                                                               options.Level = System.IO.Compression.CompressionLevel.Optimal);
        services.AddResponseCompression(options =>
                                        {
                                            options.Providers.Add<GzipCompressionProvider>();
                                            options.EnableForHttps = true;
                                        });

        // Add Azure SignalR Support
        services.AddSignalR(options => { options.EnableDetailedErrors = true; })
                .AddAzureSignalR();

        // Add MVC
        services.AddCorrelationId(); // used by the httpclient
        services.AddMvc()
            .AddJsonOptions(
                options =>
                {
                    options.SerializerSettings.ContractResolver = new DxContractResolver();
                    options.SerializerSettings.Converters.Add(new StringEnumConverter());

                    /* DxContractResolver will not send null when serialize object, but require to handle null when deserialize json */
                    // options.SerializerSettings.NullValueHandling = NullValueHandling.Ignore;
                })
            .SetCompatibilityVersion(CompatibilityVersion.Version_2_0)
            .Services
            .AddPolicies(Configuration)
            .AddHttpClient<IAzureFunctionClient, AzureFunctionClient, AzureFunctionClientOptions>(Configuration, nameof(Dx1Configuration.AzureFunctionClient));

        // Add Swagger support
        services.AddSwaggerGen(c => { c.SwaggerDoc("v1", new Info { Title = "LSK DMS API", Version = "v1" }); });

        // Add IdentityServer4 Authentication support
        services.AddAuthentication(options =>
        {
            options.DefaultScheme = "Cookies";
            options.DefaultChallengeScheme = "oidc";
        })
            .AddCookie("Cookies")
            .AddOpenIdConnect("oidc", options =>
            {
                options.SignInScheme = "Cookies";

                options.Authority = Configuration["Authentication:IdentityServer:Authority"];
                options.RequireHttpsMetadata = false;

                options.ClientId = Configuration["Authentication:IdentityServer:ClientCredential:ClientId"];
                options.ClientSecret = Configuration["Authentication:IdentityServer:ClientCredential:ClientSecret"];
                options.ResponseType = "code id_token";

                options.SaveTokens = true;
                options.GetClaimsFromUserInfoEndpoint = true;

                options.Scope.Add(Configuration["Authentication:IdentityServer:ApiName"]);
                options.Scope.Add("openid");
                options.Scope.Add("profile");
                options.Scope.Add("email");
                options.Scope.Add("offline_access");
            })
            .AddIdentityServerAuthentication(options =>
            {
                options.Authority = Configuration["Authentication:IdentityServer:Authority"];
                options.RequireHttpsMetadata = false;
                options.ApiName = Configuration["Authentication:IdentityServer:ApiName"];
                options.ApiSecret = Configuration["Authentication:IdentityServer:ClientCredential:ClientSecret"];

                options.EnableCaching = true;
                options.CacheDuration = TimeSpan.FromMinutes(10); // that's the default
            });

        services.AddSingleton<IConfigureOptions<TelemetryConfiguration>, AppInsightsConfiguration>();
    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public static void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
            app.UseBrowserLink();
        }
        else
        {
            app.UseExceptionHandler("/Home/Error");
        }

        app.UseCorrelationId();
        app.UseAppInsightProcessor();
        app.UseAuthentication();
        app.UseStaticFiles();
        app.UseSignalR(route =>
        {
            route.MapHub<DxCoreHub>("/DxCoreHub");
        });
        app.UseSwagger();
        app.UseSwaggerUI(c =>
        {
            c.RoutePrefix = string.Empty;
            c.SwaggerEndpoint("/swagger/v1/swagger.json", "API V1");
        });
        app.UseMvc(routes =>
                   {
                       routes.MapRoute(
                           "default",
                           "{controller=Home}/{action=Index}/{id?}");
                   });
    }

And I will get the following error when I try to run
System.InvalidOperationException: 'AddAzureSignalR(...)' was called without a matching call to 'IApplicationBuilder.UseAzureSignalR(...)'.
at Microsoft.Azure.SignalR.ServiceLifetimeManager1..ctor(IServiceConnectionManager1 serviceConnectionManager, IClientConnectionManager clientConnectionManager, IHubProtocolResolver protocolResolver, ILogger`1 logger, AzureSignalRMarkerService marker)
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitSingleton(SingletonCallSite singletonCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitSingleton(SingletonCallSite singletonCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.b__0(ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType)
at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)
at Microsoft.Extensions.Internal.ActivatorUtilities.GetServiceOrCreateInstance[T](IServiceProvider provider)
at Microsoft.AspNetCore.Connections.ConnectionBuilderExtensions.UseConnectionHandler[TConnectionHandler](IConnectionBuilder connectionBuilder)
at Microsoft.AspNetCore.SignalR.SignalRConnectionBuilderExtensions.UseHub[THub](IConnectionBuilder connectionBuilder)
at Microsoft.AspNetCore.SignalR.HubRouteBuilder.<>c__3`1.b__3_0(IConnectionBuilder builder)
at Microsoft.AspNetCore.Http.Connections.ConnectionsRouteBuilder.MapConnections(PathString path, HttpConnectionDispatcherOptions options, Action`1 configure)
at Microsoft.AspNetCore.SignalR.HubRouteBuilder.MapHub[THub](PathString path, Action`1 configureOptions)
at Microsoft.AspNetCore.SignalR.HubRouteBuilder.MapHub[THub](PathString path)
at Dx1.Web.Startup.<>c.b__5_0(HubRouteBuilder route) in C:\LSK\ClientApp\Dx1.Web\Startup.cs:line 164
at Microsoft.AspNetCore.Builder.SignalRAppBuilderExtensions.<>c__DisplayClass0_0.b__0(ConnectionsRouteBuilder routes)
at Microsoft.AspNetCore.Builder.ConnectionsAppBuilderExtensions.UseConnections(IApplicationBuilder app, Action`1 configure)
at Microsoft.AspNetCore.Builder.SignalRAppBuilderExtensions.UseSignalR(IApplicationBuilder app, Action`1 configure)
at Dx1.Web.Startup.Configure(IApplicationBuilder app, IHostingEnvironment env) in C:\LSK\ClientApp\Dx1.Web\Startup.cs:line 162
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure(IApplicationBuilder app)
at Microsoft.AspNetCore.Mvc.Internal.MiddlewareFilterBuilderStartupFilter.<>c__DisplayClass0_0.g__MiddlewareFilterBuilder|0(IApplicationBuilder builder)
at Microsoft.AspNetCore.Server.IISIntegration.IISSetupFilter.<>c__DisplayClass4_0.b__0(IApplicationBuilder app)
at Microsoft.AspNetCore.HostFilteringStartupFilter.<>c__DisplayClass0_0.b__0(IApplicationBuilder app)
at Microsoft.AspNetCore.Hosting.Internal.AutoRequestServicesStartupFilter.<>c__DisplayClass0_0.b__0(IApplicationBuilder builder)
at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()
I do not seem to be having the same issue as above or am I?
any ideas

The exception message explains what the problem is, specifically:
System.InvalidOperationException: 'AddAzureSignalR(...)' was called without a matching call to 'IApplicationBuilder.UseAzureSignalR(...)'.

You haven't called  UseAzureSignalR as a replacement for UseSignalR in the Configure method.

Doh, thanks.  amazing the number of hours you waste when the answer is right there.  Again thanks

I have similar issue but on AspNetcore UseSignalR

authors: Jaternius Olusheenor curtisconner davidfowl gavilanch xscript

repo: Azure/azure-signalr


text:
What's the easiest way of getting all the versionIDs for a blob?

The API reference didn't have a clear answer

Hi! There are many ways to get versionIDs for blobs. VersionIDs can be found in responses returned by multiple methods such as GetProperties, SetMetadata, etc and can be accessed using the VersionId() method mentioned in API reference (https://pkg.go.dev/github.com/Azure/azure-storage-blob-go/azblob). I've listed a few examples below to help!
You can refer to the tests to help in getting the versionID (https://github.com/Azure/azure-storage-blob-go/blob/master/azblob/zt_blob_versioning_test.go).
Here are a few examples:

Digging through the rawResponse:
https://github.com/Azure/azure-storage-blob-go/blob/d80c8c7c7c4385e4afe4ebdaab9b31efd7d87eb1/azblob/zt_blob_versioning_test.go#L70

Using VersionId() method:
https://github.com/Azure/azure-storage-blob-go/blob/d80c8c7c7c4385e4afe4ebdaab9b31efd7d87eb1/azblob/zt_blob_versioning_test.go#L29

Please let me know if you need any extra clarification!

The question was about getting all available VersionIDs for a blob. How can I do this?

Hi @maaft ! You can use the ListBlobsFlagSegment() method to get all the versions.
https://github.com/Azure/azure-storage-blob-go/blob/b32b5e3579400739418747a71c4bffaf8a19c4a0/azblob/url_container.go#L236
Here is an example from the test file zt_blob_verisioning.go:
https://github.com/Azure/azure-storage-blob-go/blob/b32b5e3579400739418747a71c4bffaf8a19c4a0/azblob/zt_blob_versioning_test.go#L108
This test file has other examples as well! Since you are trying to get versions for a specific blob, I would recommend adding a prefix in the ListBlobSegmentOptions. So something like this:
listResp, err := containerURL.ListBlobsHierarchySegment(ctx, marker, <delimiter>, ListBlobsSegmentOptions{Prefix: <blobname>, Details: BlobListingDetails{Versions: t.true}})
I hope this helps! Let me know if you have any other questions!

authors: deep-nag maaft siminsavani-msft

repo: Azure/azure-storage-blob-go


text:
Fix the ASL redefinition problem in Cocoapod for XCode 8

Updated the podspec to not include ASL and eliminated documentation warnings when users build the pod in their project.

@zezha-msft,
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

authors: msftclas zezha-msft

repo: Azure/azure-storage-ios

license: mit

license_source: bigquery


text:
Make "connection" NameResolver behavior consistent

For "connection" properties the value provided must be an app setting name. We then "auto resolve" this to the app setting value at runtime. We do this for properties in general as well, but only if those values request resolution via %% syntax (see example below). We actually DONT allow you to specify the %% on the connection property value. This is somewhat inconsistent, and some users have commented (see SO post).
We should probably support %% syntax for connection properties as well, perhaps changing our default portal logic to start injecting them for the value, once the runtime allows them. Note that any changes here will require updates to the portal picker as well.
{
    "bindings": [
        {
            "type": "eventHubTrigger",
            "name": "input",
            "direction": "in",
            "connection": "AzureWebJobsEventHubReceiver",
            "path": "%AzureWebJobsEventHubPath%",
            "consumerGroup": "$Default"
        },
        {
            "type": "eventHub",
            "name": "output",
            "direction": "out",
            "connection": "AzureWebJobsEventHubSender",
            "path": "%AzureWebJobsEventHubPath%"
        }
    ]
}

However, the reason it is the way it is now is because unlike other values that we allow raw values for (values that won't be auto resolved), for connection we do not  - the value must ALWAYS be the name of an app setting. Indeed, according to NameResolver rules, if %MyConnection% was specified, it actually means to name resolve the %MyConnection% value to get the name of the connection app setting name (a double indirection).
So I'm not sure now whether we should really change this - let's discuss.

Suggestion: %% is ignored in "connection" so it remains semantically similar without having to understand the difference (for people doing best practice). Needs more discussion.

To summarize the current state of things -- from the WebJobs perspective, you can have a string property that will be handled in one of the following ways:

it can be a literal and have no replacements performed
it can have all '%token%' strings replaced
it can be treated as the entire string is a token to be replaced (to prevent people from checking in secrets). I recently changed a bunch of WebJob Extension properties that use this pattern to end with Setting as a convention.

If we think that preventing secret check-in is valuable (I do) -- then we need a way to restrict some properties from ever being treated as literals. And we need to make it clear (docs maybe?) that some properties, notably 'connection', behave this way.
Whether we also allow them to be wrapped in %% is another question -- we could just auto-strip any trailing or ending %% as Chris suggests before we try to resolve. I guess if you really want to use '%%' in your app settings, then you'd need to double them up.
I do wonder if that is just begging for subtle little differences popping up from extensions (that may or may not use our helpers to do this) -- and whether it's worth it. Someone poking around by wrapping 'connection' in '%%' may think 'Oh okay then I can remove %% to use a literal!'. But then that doesn't do what they expect based on the other properties. It feels easier to just say 'This is a setting property, meant to indicate a setting name. We look it up directly'. Our errors could make the rules clear that if we can't find a setting after calling Resolve().
My vote would be to improve the error messages and docs in the interest of keeping the behavior simpler. I'd also wonder if we need to separate scenario 1 and 2 above -- is there any reason that we shouldn't just always try to replace? Then we can explain in wiki/docs/etc that we have two kinds of properties...
Linking some related issues:

https://github.com/projectkudu/AzureFunctionsPortal/issues/117 (this has obviously confused me in the past)
https://github.com/Azure/azure-webjobs-sdk/issues/653

@brettsam I believe we're done with this work.

authors: brettsam christopheranderson mathewc

repo: Azure/azure-webjobs-sdk-script


text:
Integrate dev --> fsharp

Integrate dev --> fsharp (independent of #544)

Hi @dsyme, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

wrong target branch

authors: dnfclas dsyme


text:
feat: API version update avm/res/databricks/workspace

Description
I have updated all the resources in the databricks workspace to use the latest verison of API
Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] I have run Set-AVMModule locally to generate the supporting module files.
[x] My corresponding pipelines / checks run clean and green without any errors or warnings

@clintgrove - Please resolve the conflict, there has been some adjustments to the telemetry deployment used as per #2353

@clintgrove - Please resolve the conflict, there has been some adjustments to the telemetry deployment used as per #2353

Edit (@AlexanderSehr): Please just include latest main & regenerate the main.json file:

Hi @ChrisSidebotham  I have resolved conflicts, can you double check I got it right. thanks

@clintgrove - Please resolve the conflict, there has been some adjustments to the telemetry deployment used as per #2353

Edit (@AlexanderSehr): Please just include latest main & regenerate the main.json file:

Hi @ChrisSidebotham I have resolved conflicts, can you double check I got it right. thanks

Hey @clintgrove,
the perge of the previous PE update also touched on the JSON, causing conflicts. Please merge latest main into your branch (and or use the Resolve conflicts button on the PR) and run the JSON compilation locally again to update it to the 'real' combined latest

repo: Azure/bicep-registry-modules


text:
feat: Restored features of CARML AMA PR

Description

Retored the functionality introduced by PR https://github.com/Azure/ResourceModules/pull/3938
Updated Set-AVMModule utility to be able to handle modules that don't use plane test names like max but instead e.g., <prefix>.max
Small update to docs and regeneration of files
Shifted deployment location as encountering capacity issues in WestEurope
Added a warning supression for Network/Connection that was added for the same reason

Pipeline

Looks good to me as per requested changes. Approving but not resolving @rahalan comment so that he can have the last saying as module owner.

authors: AlexanderSehr eriqua


text:
Requesting a change in dependsOn expression

Bicep version
Bicep CLI version 0.8.9 (33a85174de)
Describe the bug
I found an issue while decompiling an ARM Template (PlExample01_Original.json) using below command. I found that reference to PlExample02 is not taken care.
bicep decompile PlExample01_Original.json --outfile PlExample01.bicep --force
The error message
PlExample01.bicep(52,5) : Error BCP034: The enclosing array expected an item of type "module[] | (resource | module) | resource[]", but the provided item was of type "string".
To Reproduce
bicep decompile PlExample01_Original.json --outfile PlExample01.bicep --force
Manual correction
I explicitly mentioned the dependsOn field to a resource in bicep file (PlExample01_corrected.bicep). After correction build action produced the dependsOn property as shown below, expression result in valid value but long expression with unnecessary split functions.
"dependsOn": [
        "[resourceId('Microsoft.DataFactory/factories/pipelines', split(format('{0}/PlExample02', parameters('factoryName')), '/')[0], split(format('{0}/PlExample02', parameters('factoryName')), '/')[1])]"
      ]

PlExample01_Original.json
{
	"$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
	"contentVersion": "1.0.0.0",
	"parameters": {
		"factoryName": {
			"type": "string",
			"metadata": "Data Factory name"
		}
	},
	"variables": {
		"factoryId": "[concat('Microsoft.DataFactory/factories/', parameters('factoryName'))]"
	},
	"resources": [
		{
			"name": "[concat(parameters('factoryName'), '/PlExample01')]",
			"type": "Microsoft.DataFactory/factories/pipelines",
			"apiVersion": "2018-06-01",
			"properties": {
				"activities": [
					{
						"name": "Wait1",
						"type": "Wait",
						"dependsOn": [],
						"userProperties": [],
						"typeProperties": {
							"waitTimeInSeconds": {
								"value": "@pipeline().parameters.TimeToWait",
								"type": "Expression"
							}
						}
					},
					{
						"name": "Execute Pipeline1",
						"type": "ExecutePipeline",
						"dependsOn": [
							{
								"activity": "Wait1",
								"dependencyConditions": [
									"Succeeded"
								]
							}
						],
						"userProperties": [],
						"typeProperties": {
							"pipeline": {
								"referenceName": "PlExample02",
								"type": "PipelineReference"
							},
							"waitOnCompletion": true
						}
					}
				],
				"parameters": {
					"TimeToWait": {
						"type": "Int",
						"defaultValue": 5
					}
				},
				"annotations": [],
				"lastPublishTime": "2022-07-14T12:46:14Z"
			},
			"dependsOn": [
				"[concat(variables('factoryId'), '/pipelines/PlExample02')]"
			]
		},
		{
			"name": "[concat(parameters('factoryName'), '/PlExample02')]",
			"type": "Microsoft.DataFactory/factories/pipelines",
			"apiVersion": "2018-06-01",
			"properties": {
				"activities": [
					{
						"name": "Wait1",
						"type": "Wait",
						"dependsOn": [],
						"userProperties": [],
						"typeProperties": {
							"waitTimeInSeconds": 1
						}
					}
				],
				"annotations": []
			},
			"dependsOn": []
		}
	]
}

PlExample01.bicep
param factoryName string

var factoryId = 'Microsoft.DataFactory/factories/${factoryName}'

resource factoryName_PlExample01 'Microsoft.DataFactory/factories/pipelines@2018-06-01' = {
  name: '${factoryName}/PlExample01'
  properties: {
    activities: [
      {
        name: 'Wait1'
        type: 'Wait'
        dependsOn: []
        userProperties: []
        typeProperties: {
          waitTimeInSeconds: {
            value: '@pipeline().parameters.TimeToWait'
            type: 'Expression'
          }
        }
      }
      {
        name: 'Execute Pipeline1'
        type: 'ExecutePipeline'
        dependsOn: [
          {
            activity: 'Wait1'
            dependencyConditions: [
              'Succeeded'
            ]
          }
        ]
        userProperties: []
        typeProperties: {
          pipeline: {
            referenceName: 'PlExample02'
            type: 'PipelineReference'
          }
          waitOnCompletion: true
        }
      }
    ]
    parameters: {
      TimeToWait: {
        type: 'Int'
        defaultValue: 5
      }
    }
    annotations: []
    lastPublishTime: '2022-07-14T12:46:14Z'
  }
  dependsOn: [
    '${factoryId}/pipelines/PlExample02'
  ]
}

resource factoryName_PlExample02 'Microsoft.DataFactory/factories/pipelines@2018-06-01' = {
  name: '${factoryName}/PlExample02'
  properties: {
    activities: [
      {
        name: 'Wait1'
        type: 'Wait'
        dependsOn: []
        userProperties: []
        typeProperties: {
          waitTimeInSeconds: 1
        }
      }
    ]
    annotations: []
  }
  dependsOn: []
}

PlExample01_corrected.bicep
param factoryName string

var factoryId = 'Microsoft.DataFactory/factories/${factoryName}'

resource factoryName_PlExample01 'Microsoft.DataFactory/factories/pipelines@2018-06-01' = {
  name: '${factoryName}/PlExample01'
  properties: {
    activities: [
      {
        name: 'Wait1'
        type: 'Wait'
        dependsOn: []
        userProperties: []
        typeProperties: {
          waitTimeInSeconds: {
            value: '@pipeline().parameters.TimeToWait'
            type: 'Expression'
          }
        }
      }
      {
        name: 'Execute Pipeline1'
        type: 'ExecutePipeline'
        dependsOn: [
          {
            activity: 'Wait1'
            dependencyConditions: [
              'Succeeded'
            ]
          }
        ]
        userProperties: []
        typeProperties: {
          pipeline: {
            referenceName: 'PlExample02'
            type: 'PipelineReference'
          }
          waitOnCompletion: true
        }
      }
    ]
    parameters: {
      TimeToWait: {
        type: 'Int'
        defaultValue: 5
      }
    }
    annotations: []
    lastPublishTime: '2022-07-14T12:46:14Z'
  }
  dependsOn: [
    factoryName_PlExample02
  ]
}

resource factoryName_PlExample02 'Microsoft.DataFactory/factories/pipelines@2018-06-01' = {
  name: '${factoryName}/PlExample02'
  properties: {
    activities: [
      {
        name: 'Wait1'
        type: 'Wait'
        dependsOn: []
        userProperties: []
        typeProperties: {
          waitTimeInSeconds: 1
        }
      }
    ]
    annotations: []
  }
  dependsOn: []
}

PlExample01_corrected.json
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "metadata": {
    "_generator": {
      "name": "bicep",
      "version": "0.8.9.13224",
      "templateHash": "5656674683713888465"
    }
  },
  "parameters": {
    "factoryName": {
      "type": "string"
    }
  },
  "variables": {
    "factoryId": "[format('Microsoft.DataFactory/factories/{0}', parameters('factoryName'))]"
  },
  "resources": [
    {
      "type": "Microsoft.DataFactory/factories/pipelines",
      "apiVersion": "2018-06-01",
      "name": "[format('{0}/PlExample01', parameters('factoryName'))]",
      "properties": {
        "activities": [
          {
            "name": "Wait1",
            "type": "Wait",
            "dependsOn": [],
            "userProperties": [],
            "typeProperties": {
              "waitTimeInSeconds": {
                "value": "@pipeline().parameters.TimeToWait",
                "type": "Expression"
              }
            }
          },
          {
            "name": "Execute Pipeline1",
            "type": "ExecutePipeline",
            "dependsOn": [
              {
                "activity": "Wait1",
                "dependencyConditions": [
                  "Succeeded"
                ]
              }
            ],
            "userProperties": [],
            "typeProperties": {
              "pipeline": {
                "referenceName": "PlExample02",
                "type": "PipelineReference"
              },
              "waitOnCompletion": true
            }
          }
        ],
        "parameters": {
          "TimeToWait": {
            "type": "Int",
            "defaultValue": 5
          }
        },
        "annotations": [],
        "lastPublishTime": "2022-07-14T12:46:14Z"
      },
      "dependsOn": [
        "[resourceId('Microsoft.DataFactory/factories/pipelines', split(format('{0}/PlExample02', parameters('factoryName')), '/')[0], split(format('{0}/PlExample02', parameters('factoryName')), '/')[1])]"
      ]
    },
    {
      "type": "Microsoft.DataFactory/factories/pipelines",
      "apiVersion": "2018-06-01",
      "name": "[format('{0}/PlExample02', parameters('factoryName'))]",
      "properties": {
        "activities": [
          {
            "name": "Wait1",
            "type": "Wait",
            "dependsOn": [],
            "userProperties": [],
            "typeProperties": {
              "waitTimeInSeconds": 1
            }
          }
        ],
        "annotations": []
      }
    }
  ]
}

As far as actually deploying the Bicep file, the split doesn't cause any problems - the expression will be evaluated by the Deployment Engine to the correct value.
If you're interested, here's how I'd refactor further to be a a bit more idiomatic; avoiding formatting resource names with /:
param factoryName string

resource factory 'Microsoft.DataFactory/factories@2018-06-01' existing = {
  name: factoryName
}

resource plExample01 'Microsoft.DataFactory/factories/pipelines@2018-06-01' = {
  parent: factory
  name: 'PlExample01'
  properties: {
    activities: [
      {
        name: 'Wait1'
        type: 'Wait'
        dependsOn: []
        userProperties: []
        typeProperties: {
          waitTimeInSeconds: {
            value: '@pipeline().parameters.TimeToWait'
            type: 'Expression'
          }
        }
      }
      {
        name: 'Execute Pipeline1'
        type: 'ExecutePipeline'
        dependsOn: [
          {
            activity: 'Wait1'
            dependencyConditions: [
              'Succeeded'
            ]
          }
        ]
        userProperties: []
        typeProperties: {
          pipeline: {
            referenceName: 'PlExample02'
            type: 'PipelineReference'
          }
          waitOnCompletion: true
        }
      }
    ]
    parameters: {
      TimeToWait: {
        type: 'Int'
        defaultValue: 5
      }
    }
    annotations: []
    lastPublishTime: '2022-07-14T12:46:14Z'
  }
  dependsOn: [
    plExample02
  ]
}

resource plExample02 'Microsoft.DataFactory/factories/pipelines@2018-06-01' = {
  parent: factory
  name: 'PlExample02'
  properties: {
    activities: [
      {
        name: 'Wait1'
        type: 'Wait'
        dependsOn: []
        userProperties: []
        typeProperties: {
          waitTimeInSeconds: 1
        }
      }
    ]
    annotations: []
  }
}

This'll result in the dependsOn being generated with a simpler expression:
"dependsOn": [
  "[resourceId('Microsoft.DataFactory/factories/pipelines', parameters('factoryName'), 'PlExample02')]"
]

authors: anthony-c-martin syedhamjath

repo: Azure/bicep


text:
Support for user defined functions

See https://github.com/Azure/bicep/blob/ant/exp/func/src/Bicep.Core.Samples/Files/Functions_LF/main.bicep for a syntax example.
Notes/limitations:

UDFs in JSON require declaring the return type, so I've modified the spec to require the user to declare the return type.
User-defined types in UDF params & outputs are unsupported.
UDFs are currently quite limited - they can't call UDFs, or access outer scoped variables.
This is currently behind an experimental feature flag ("userDefinedFunctions")

Closes #447
Closes #9239
Microsoft Reviewers: Open in CodeFlow

We don't support user-defined types in UDF params & outputs. Should we block this, or attempt to support it?

It would be a small-ish change in the ARM runtime to support user-defined types, and if it were up to me, I would rather put in the effort to close that feature gap than document and field questions about the limitation.
But it did get me thinking: because types can contain symbolic references to other types, I can't think of any reason we would allow user-defined types and still disallow references to variables and parameters. Should we look at removing that restriction on UDFs, too?

But it did get me thinking: because types can contain symbolic references to other types, I can't think of any reason we would allow user-defined types and still disallow references to variables and parameters. Should we look at removing that restriction on UDFs, too?

I think so - I just wanted to keep the initial implementation as simple as possible. One complexity is that UDFs overloads parameters(...) to refer to parameters of the UDF and not parameters of the template. We'd most likely need to introduce scoping rules to deal with this.

🤩🎉🚀

Support to outer scoped variables and include/import feature would be very useful

authors: SimonWahlin anthony-c-martin ayoussef-insight jeskew


text:
[POC] Update the output directory of compiled JS

WIP description.

Closing as this is not the right fix.

repo: Azure/brigadier


text:
Raspberry Pi 3 as a Gateway Device unable to connect IoT Hub

I am building the Connect The Dots Project with Arduino UNO + Sparkfun Weather Shield and using Raspberry Pi as a Gateway by connect Arduino to RPi3 with USB.
I followed the instruction strictly but it still not work.  In RPi3, Gateway service is running but unable to connect to Azure IoT Hub.
I have ensure that IoT Hub is work by using the sample Node.js code to send the message to the IoT Hub.
Could you please help guide on how to diagnose the issue on RPi3?

Hi @bunpotth
Sorry for the late response, I was out on vacation the last 2 weeks :-)
Here are a few things to try and dentify what's going wrong.
Are you building the gateway project in debug or release? try debug if you were using release.
Also, search for the logs subfolder in the gateway app folder on the device to see if you can see any relevant info in there.

Thank you very for your advice. I will try this on this weekend.
On Tuesday, 23 August 2016, Olivier Bloch notifications@github.com wrote:

Hi @bunpotth https://github.com/bunpotth
Sorry for the late response, I was out on vacation the last 2 weeks :-)
Here are a few things to try and dentify what's going wrong.
Are you building the gateway project in debug or release? try debug if you
were using release.
Also, search for the logs subfolder in the gateway app folder on the
device to see if you can see any relevant info in there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/connectthedots/issues/247#issuecomment-241773069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA52_e6-NvsMhZs8tWPRrg-jnhfRAX0Nks5qixL7gaJpZM4JefYv
.

hi @bunpotth
Any success? I'd like to narrow this issue down and any input would be helpful
Thanks

Closing because stale. reopen if needed

authors: bunpotth olivierbloch

repo: Azure/connectthedots


text:
Canary deployment error

Repro steps:

Version 0.0.1 deployment without canary (5 replicas; in namespace meshed with linkerd)

Version 0.0.2 deployment with canary using the following YAML:

uses: azure/k8s-deploy@v1
with:
namespace: go-template
manifests: ${{ steps.bake.outputs.manifestsBundle }}
images: |
ghcr.io/USER/IMG:${{ env.IMAGE_TAG }}
strategy: canary
percentage: 20
traffic-split-method: smi
baseline-and-canary-replicas: 1

Current behaviour:

Canary deployment of 0.0.2 fails with the following error: StableSpecSelectorNotExist : deploymentname

Expected behaviour:

Canary deployment succeeds with SMI TrafficSplit

Extra information:

canary deployment succeeds without SMI
namespace of the deployment has the following linkerd annotation - linkerd.io/inject: enabled
also tried without baseline-and-canary-replicas - same issue

@gbaeke have you tried using one of our latest versions? v1.4 or v1.3 maybe?

@gbaeke have you tried using one of our latest versions? v1.4 or v1.3 maybe?

@ds-ms I tried both 1.3 and 1.4 without luck

@ds-ms I tried both 1.3 and 1.4 without luck

Any news on this topic? I'm running the same issue :(

Hi,
I documented my experience in this blog post: https://blog.baeke.info/2021/01/11/kubernetes-canary-deployments-with-github-actions/. Following the steps in the post, I did not have the issue.

Great, thanks @gbaeke will take a look

So it worked @gbaeke , it seems, as far as I understand, you have to deploy the first time using this tasks from scratch, as if a previous deployment already exists get stuck

you have to deploy the first time using this tasks from scratch, as if a previous deployment already exists get stuck

That is correct. We took this decision consciously to avoid breaking existing setups accidentally.

authors: ds-ms gbaeke lfraile


text:
Don't expose fetch types in HttpOperationResponse

Pulls HttpHeaders class as-is from httpPipeline branch

Simplifies msRest.ts because I found out export { ... } from "other-module" is a thing

Is there a reason for HttpOperationResponse itself to be a class type? Seems like maybe not since any HttpClient implementation can implement the interface with their own class type. If you don't agree I can change the interface I have there to be some "properties" type which is used as a constructor argument.

Thinking of just providing the HttpOperationResponse directly in the generated code in the streaming case. Any apparent reason to do it differently?

BTW corresponding PRs need to be opened in ms-rest-azure-js and autorest.typescript because this is a breaking change.

repo: Azure/ms-rest-js


text:
Groups for notification service are absent in TenantInfo and UserInfo

The following groups are to be added.

Pubsub
Ops
Cron

Can we please relocate this issue into Gitlab and follow the pattern now being established.

authors: danielscholl komakkar

repo: Azure/osdu-infrastructure


text:
Add Action to Rule Definition

Type of change?

[ ] Bug fix
[x] New feature
[ ] Enhancement
[ ] Breaking change (breaks backward compatibility)

Description, Context, Motivation
Add option to include an email action in a rule definition. Added PillContainer and Pill components for email representation in flyout.
Checklist:

[x] All tests passed
[x] The code follows the code style and conventions of this project
[ ] The change requires a change to the documentation
[ ] I have updated the documentation accordingly

This change is

"pill" is what the selected emails show up in:

@isaac73  and @spryor Can you look at this PR.

authors: molly-moen ppathan

repo: Azure/pcs-remote-monitoring-webui


text:
Consider adding a version number to checklists

Currently, when checklists are shared around, there is no indication of when the checklist content was imported. For example, if an XLSX file is being passed around to bypass client-side restrictions on macros, the spreadsheet may contain outdated content depending on when it was generated.
Consider adding a version number or "Imported Date" to the pre-generated XLSX files and to the macro import checklist action.

@mbrat2005 This is a very good idea. We recently changed the structure of the Github action doing the automated translation, and now we are finally in a position to automatically add a timestamp to the metadata of the checklists after a push.

Hey @mbrat2005 is the current timestamping of the checklists enough?

Yes @erjosito, the import info looks great and should help! I'll close this issue, thanks for addressing it!

repo: Azure/review-checklists


text:
Questions: swa start

Have a few questions about parts of the start command that are unclear...

What's the "context" and how does that differ from appLocation or appArtifactLocation?

If I have a folder named static and I want to serve it, it seems like the only way to make this work is to set the context: swa start ./static. swa start --app-location ./static (or using --app) doesn't seem to work.

How does it select the workflow file to use, especially if there's more than one?
What does it use from the workflow?
How does --build work?
How does it determine which config file to use? #125

Great questions! Let's talk about this during our next call and then I'll write down the answers in the wiki.

What's the "context" and how does that differ from appLocation or appArtifactLocation?

context determines how the emulator will serve the static content:

if context is a folder, then we will start the emulator and serve static content from that folder
if context is an HTTP address, then we will start the emulator and proxy req to the dev server

In both cases, we reconfigure appLocation and appArtifactLocation to reflect that:

appArtifactLocation = context
appLocation = cwd() (currently, we don't use appLocation if context is a dev server)

If I have a folder named static and I want to serve it, it seems like the only way to make this work is to set the context: swa start ./static. swa start --app-location ./static (or using --app) doesn't seem to work.

swa start --app-location ./static is the old way. Technically speaking this:
swa start --app-location ./static

translates to this:
swa start <context> --app-location ./static

When not provided, context maps to the pwd:
swa start ./ --app-location ./static

My understanding of how commander works, is that context (a command) will take precedence over --app-location (an options). But I am sure with a little of checks we can change that.

How does it select the workflow file to use, especially if there's more than one?

The scans scans for azure-static-web-apps-**.yml files under cwd()/.github/workflows/, and picks the 1st one (non-deterministic!).

What does it use from the workflow?

app_build_command
api_build_command
app_location
app_artifact_location
api_location

These values are overridden by user's config (CLI flags).

How does --build work?

We check for runtime type. We currently support Node.js and .NET (experimental):

For Node.js,

For app, we invoke npm install && <app_build_command>
For api we invoke npm install && <api_build_command>

For .NET,

We invoke dotnet build

Important: We don't build if context is a dev server.

How does it determine which config file to use

We scan recursively the appLocation for staticwebapp.config.json (or routes.json):

If we find both staticwebapp.config.json and routes.json, we pick staticwebapp.config.json.
If we find only routes.json, verify it's a valid SWA config file (see #) then pick it.

Hi @anthonychu , i was trying to implement Static Web apps and add API to it as described in this document - https://docs.microsoft.com/en-us/azure/static-web-apps/add-api?tabs=vanilla-javascript but seems i am having problem running this command on my bash terminal. "swa start src --api-location api"
I get below error when i try to run it, i am not sure if i missed anything to install or configure. I have followed all the steps mentioned in this document already.

I am using Windows machine , and running the code from the root directory.

Hi @Divyesh85 ,
Sorry that you faced this issue. Could you please confirm if you followed the Installation steps mentioned above? One usually comes across this error when the SWA CLI is not installed, hence the bash is not able to recognise the command swa
Also, it would be great if you could help us repro the error by sharing your project in a public repository if possible.
Hope this helps!

@Reshmi-Sriram sorry for late reply due to holidays, i was able to resolve the issue, seems by default when i was trying to install azure functions and azure static webapps cli on VS code terminal it was not installing using the administrator mode hence was not able to install properly. I tried it in separate command prompt as an admin and it went well. Thanks for the prompt reply though.

@Reshmi-Sriram sorry for late reply due to holidays, i was able to resolve the issue, seems by default when i was trying to install azure functions and azure static webapps cli on VS code terminal it was not installing using the administrator mode hence was not able to install properly. I tried it in separate command prompt as an admin and it went well. Thanks for the prompt reply though.

authors: Divyesh85 Reshmi-Sriram anthonychu manekinekko

repo: Azure/static-web-apps-cli