Cannot see the Artifacts section on Azure devops - azure

I have been given admin access to our Azure devops environment. But I cannot seem to access the Artifacts section. It is as showm below:
I have checked with my team, they can see the different options there.But I do not see anything. On some debugging into the developer tools, I observed the following issues:
On the issues section, I see the following:
What is the solution here? Any suggestions?

Related

Where are the errors located in the Azure portal GUI?

Where are the errors located in the Azure portal GUI?
Abstract
I'm currently developing a Flask app, deploying it on Azure.
I've configured CI/CD with GitHub. Each push to the desired branch causes the thing to build.
There seems, however, to be a problem with this build that I need to discover.
Despite my great effort, despite reading a few pages of Azure docs and a few answers on this site, I cannot seem to find the actual location that would show me the Azure build errors I want to see.
What have I tried
Log Analytics
I've configured Log Analytics. I can't remember its function, but it was necessary to enable some logging.
GUI
I've checked the Logs tab for my AppService. Although I've noticed a few errors, these look as unhelpful as this:
If this is the most I would get, please note that in the comments.
Log Streaming
I've started streaming logs in VS Code. These only tell me that An unknown error has occurred. Check the diagnostic log for details.
Downloading logs from app's subdirectory
Although I cannot pin-point the exact article, there is a way of downloading logs from the app's endpoint. I did it, got two files and the most I would get is ERROR - Container for *app name* site *app name* is unhealthy, Stopping site.
Again, if this is meaningful for a rudimentary Flask app deployed in CI/CD pipeline with no tampering in the settings of Azure, let me know.
Wrapping up
Are the samples shown valid, meaningful errors? If not, where can I find more information?
I have tried to reproduce the issue by configuring an app with CI/CD using GitHub and integrated successfully as shown below:
if we made any changes in the repository then it will trigger a workflow and build process takes places.
If there are any errors then we can look at those errors in the github repository only by navigating to the Actions-->click on build, there you can see the errors as shown below:
You can also review the application logs, either by enabling diagnostic logging on app service to identify the cause or you can make use of application logs under (diagnose and solve problems--> availability and performance) from the portal under your web app.

Is it possible to disable manual publishing of Azure Functions?

We have an Azure Function and an Azure DevOps Pipeline, the pipeline builds and published the code of the function's repo automatically. We want to escape discrepancies caused by, potentially, people manually publishing a version of the code, from within their Visual Studio, that is not in source control.
How can we ensure that?
Is there a way to disable manual publishing and only allow the Azure DevOps Pipeline to publish code to the function?
I am referring to a person using the "Publish" option in Visual Studio. Is there a way to forbid the Azure function from accepting such a publish?
To stop manual changes to the build, yaml files and pipeline would be to restric access to the build section of the pipeline for all the users.
This way no one will be able to change the pipeline but the admin user will still have access to the pipeline.
To set the permission we have to go to manage security which is under the pipeline tag.
Then we can select the permission for the users.
Here each tag represents a permission. Since we want to stop manual deployment we would set Edit build pipeline and Edit quality pipeline to deny.
These permissions can be set for individuals as well as security group.
Reference:
permissions in devops.

Publish APIM Developer portal through terraform

Hi I have searched through docs on and can't quite find how to publish the developer portal through terraform. My terraform does spool a resource group with an API Management service resource but I want it to also publish the developer portal and enable CORS. Is this possible through terraform or has to be done manually after I have the rg spooled?
Updated terraform looking at the documentation here: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/api_management#host_name
There is a block for developer portal but I am not sure if this actually publishes it and also not sure what to put in the host_name. Please assist.
You can completely configure the APIM and its portal from an ARM template but you can't publish the content. There are scripts in the Github repo to do this using the rest API.
Publishing content using those scripts will work for the managed portal. If you're hosting your own version of the portal you'll have to take some additional steps, according to the migration script.
If you can get Terraform to execute NodeJs scripts, you should be able to use these to push content to the portal and publish it.
Please also check the docs that were recently added about the migration script.
I have never used terraform but I believe what you highlighted would only create a custom domain for your developer portal.
Hostname would be a custom domain, or you can use the default {apimname}.developer.azure-api.net. If you provide a custom domain for your developer portal you would have to provide a SSL certificate and also you have to have a CName for this custom domain.
I do no think the developer portal would be published Can I deploy everything through ARM templates now? The only thing that's not available is developer portal content. Everything else is available through ARM. link
Try creating an APIM manually and see what settings is it using for the developer portal in Azure Resource Explorer. Try to replicate those settings in your code.

Nop-Commerce MarketPlace Azure first Deployment Issue

I'm trying to use install nop-commerce from the marketplace azure.
I create the web app and setting up the sql server in the same wizard.
I'm putting both in the same resource-group name.
However, I'm getting the deploment issue below:
Deployment to resource group 'felisbabies' failed.
Additional details from the underlying API that might be helpful: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.
Anyone face this similar sceneario?
You can see here i wrote cosmetic article on it nopCommerce deployment with azure

Azure Devops Releases Agent job's Agent configuration show 'Default (No agents)'

I'm using Azure DevOps pipelines and for 'builds' I can define 'Hosted Ubuntu' agent (in my pipelines.yml file). But for 'releases' there's no way to edit yaml just the UI. The agent pool drop down list shows 'Default (no agents)'. I assume my problem is probably related to project permissions but haven't figured out what controls the visibility. On another account I see all the hosted agent options available.
For the possible security permissions issue
Check that you are part of the group(s) assigned as User to the security of the app pool in question.
If this security operates like other Allow, Deny, NotSet permissions, then your occupation in a group that has less than User permission will revoke that permission, but I haven't seen any documentation about this.
For the use of YAML in release pipelines
Yaml usage in the formal release pipeline hub is not supported. If you want to use yaml for your CD release, you're going to need to enable the new multi-stage pipelines experience.
This allows you to create stages in your .yml file that relate to deployment functions in addition to the classic build functions.
I believe this removes your release tracking from the release hub and integrates it directly into the build hub.
This is still a new concept for Azure DevOps, as is the documentation and writing about it. I found this article to be helpful.
Because this new feature seems to be centered around AKS (or other Kubernetes services) and Docker, I'm not sure if this will help you by allowing you to specify the host in yaml, but you mentioned "release" and "yaml" in the same sentence, so I thought I would address that.

Resources