I'm facing a problem when I deploy a template to build a scheduler job with an URI in which I want to pass two arguments.
I want to set as the uri something like "/api/triggeredwebjobs/MyJob/run?arguments=arg1%20arg2"
This works well when typing this through the Azure portal and the job starts without errors, but using an Azure template I see that in the uri the '?' character has been encoded to '%3F', what makes the job to fail because, the route does not exist.
I can't understand why is doing this since, no other character (like '/') is being encoded when deploying the template (at least I can't see it through the Azure portal).
Is this maybe a bug, or is it something I'm maybe doing wrong?
Greetings.
Related
I have several teams with several QA environments that need to be deployed to.
I am using the ServiceFabricDeploy#1 task to deploy but I can't find a way to change the Service Connection during the deployment.
The input has to be valid during compile time so I can't use a variable macro ( i.e. $(connectionName) is blank durin compile ).
The input has to change based on the value passed in from the UI, so if I use template expressions (i.e. ${{variables.connectionName}}) ) they pass the compile but turn to blank during runtime.
How can I pass in the Service Connection name to a YAML pipeline?
Turns out I was not using variables correctly. I was trying to pass them in through parameters. What I needed to do was use the variable macro directly.
This works:
- task: ServiceFabricDeploy#1
inputs:
applicationPackagePath: '$(Build.ArtifactStagingDirectory)\drop\pkg'
serviceConnectionName: $(connectionName)
... etc ...
As per Microsoft's documentation as on 29th June, 2020,
Service connection cannot be specified by variable
To expand upon Nitin's response, this used to work in our Classic UI-defined release pipelines - we pass $(AzureSubscription) to a number of Azure App Service Deploy tasks, and the service connection is appropriately selected.
A few days back I had to make a change to a single deployment task to modify an artifact path, and only this task started failing until I took the variable out and manually specified the service connection.
I suspect that existing pipelines may continue to work until they're modified. I'll be doing some experimentation to validate this.
I am trying to deploy a node app into azure, while doing last step of deployment
git push azure master, an error occurred as below.
fatal: unable to access 'https://lalit#wittyparrot.com#node-deploy-to-azure.scm.azurewebsites.net/node-deploy-to-azure.git/': Couldn't resolve host 'wittyparrot.com#node-deploy-to-azure.scm.azurewebsites.net'
Please help to resolove it.
One solution is like #evilSnobu has said. Use the url https://{appname}.scm.azurewebsites.com.
What you have met is caused by your deployment user name, as you use the format https://{username}#{appname}.scm.azurewebsites.net:443/{appname}.git
In your case, you set it as lalit#wittyparrot.com. You may have done this setting in Azure Cloud Shell and it showed no error.
But in fact, the name can only contain letters, numbers, hyphens and underscores. Otherwise your url can't be resolved correctly.
You can see the tip here.
Azure Cloud Shell may miss some necessary pattern check so that invalid user name causes no error to show.
As per documentation of Microsoft.Automation/automationAccounts/modules (https://learn.microsoft.com/en-us/azure/templates/microsoft.automation/automationaccounts/modules#ContentLink) it's expecting URI parameter. What exactly supposed to be at the end of that parameter? I want to push my custom module and it's possible through UI via ZIP file and I expected that I can specify ZIP with custom DSC resource but it did not work. There is no documentation I was able to find what shall appear in that URI.
You need to provide uri to your zipped dsc module ;) There are a bunch of article online that you can salvage data from. Like this.
Also, take a look here
I have an IIS, on an azure VM, that host a web application that I use to retrive data through SOAP request. Everything works fine if I access from localhost but as soon as I access to some functions from outside I get a response formally correct but with no data in it.
Configuring different VM with the same services I had the same results. I changed <httpRuntime maxRequestLength="1024000" /> because it seems the problem was related to the amount of data retrived but I had no positive result. It isn't a timeout problem because other functions return values even after 30 seconds.
Is there anything else I might I have done wrong, or that I need to configure to allow SOAP requests from my Azure web application? Where can I look for better diagnostics to see what's going wrong?
Configuring on the target VM a development environment I discovered the problem was releted to the differences of Culture set on sever and on Client.
This caused a transformation of parameters sent to sql server for data extraction.
I had to change the code to become Culture invariant.
I have a ASP.NET MVC web application project that I want to deploy to my IIS webserver. The site tree is set up thusly:
SERVERNAME(myDomain\Username)
Application Pools
Sites
Default Web Site
MyProjectSite
bin
Content
...
Views
I am trying to deploy to the MyProject site. See below settings that I am using versus the errors I am returning. I am apparently not specifying my site path correctly, but for the life of me, I can't figure out what it should be.
The following settings stay the same between iterations:
/p:DeployOnBuild=True /p:DeployTarget=MsDeployPublish /p:CreatePackageOnPublish=False /p:MSDeployPublishMethod=WMSvc /p:AuthType=Basic /p:Username="myUserName" /p:Password="MyPassword" /p:AllowUntrustedCertificate=True
Specify SiteName/ as IISAppPath:
Parameters:
/p:MsDeployServiceUrl="https://serverName:8172/MsDeploy.axd?Site=MyProjectSite" /p:DeployIisAppPath="MyProjectSite/"
Error:
Could not complete an operation with the specified provider ("createApp") when connecting using the Web Management Service - I don't want to create a new site. I want to sync the content that is already there.
Specify IISAppPath as Root (supposing that the sitename in the URL is used)
Parameters:
/p:MsDeployServiceUrl="https://serverName:8172/MsDeploy.axd?Site=MyProjectSite" /p:DeployIisAppPath="/"
Error:
Could not complete an operation with the specified provider ("iisApp") when connecting using the Web Management Service - Looks like it is trying to access the Default WebSite or something (to which I have purposefully NOT given myself rights).
Specify IISAppPath as empty string(supposing that the sitename in the URL is used)
Parameters:
/p:MsDeployServiceUrl="https://serverName:8172/MsDeploy.axd?Site=MyProjectSite" /p:DeployIisAppPath=""
Error:
The "ConcatFullServiceUrlWithSiteName" task was not given a value for the required parameter "SiteAppName" - So it interprets "" as actually a null value thus breaking an attempt to concatenate it.
Specify no site attribute in the URL but SiteName/ as IISAppPath
Parameters:
/p:MsDeployServiceUrl="https://serverName:8172/MsDeploy.axd" /p:DeployIisAppPath="MyProjectSite/"
Error:
Could not complete an operation with the specified provider ("createApp") when connecting using the Web Management Service
Specify no site attribute in URL but SiteName as IISAppPath
Parameters:
/p:MsDeployServiceUrl="https://serverName:8172/MsDeploy.axd" /p:DeployIisAppPath="MyProjectSite"
Error:
Could not complete an operation with the specified provider ("createApp") when connecting using the Web Management Service
Now given that it is running a concatenate on the SiteAppName, it must be combining it with the Site name, yes? What are you supposed to put there to get the site to sync to the root of a site?
Update
In an attempt to figure out the proper path scheme, I have tried to publish using the Visual Studio 2012 Publish dialog. In this case, I am returned an error saying that The request timed out (testing the connection works almost instantly and previewing the changes works but takes a few seconds). I checked the event log, and the tracelog for wmsvc to no avail. Even with trace set to verbose, nothing shows up in the tracelog. I have tried disabling the firewalls on both computers, and nothing seems to work on that front either.
Figured this one out.
The problem stemmed from two settings in the Web Deploy page of the project properties. I had previously set this project up (in the Debug configuration) to copy only the files necessary to run the application, and NOT build a zip package. I neglected however to do anything to those settings for the release configuration.
The reason (confidence level 75%) it was trying to use createApp was because it was deploying from the Zip package it had created. So my IISAppPath settings in those cases were fine, I was just deploying the wrong thing.
I set the Create deployment package as a zip file setting to false, and the Items to deploy dropdown to Only files needed to run this application and everything went off without a hitch.
Incidentally I found out (as referred above) that you can use the Publish Profiles outputted by the Web Publish dialog in Visual Studio (2012 only unfortunately; 2010 you have to do some massaging that I am unsure of). I named mine with no spaces, and supplied the password as an argument as well as the Untrusted Certificate setting. Now MSBuild Arguments in the build definition for TFS look like this:
/p:DeployOnBuild=True;PublishProfile=NameOfPublishProfile /p:AllowUntrustedCertificate=True /p:Password=PleaseVerifyMe