I am trying to publish my offering in Azure stack using doc https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-create-and-publish-marketplace-item?view=azs-2002.
But I have linked templates and in manifest file I have provided the paths of artifacts. But I am not clear of what does "isDefault" means ?
is there any in detail guide regarding creation and publishing an offer on Azure stack?
"isDefault" is used to denote the main template of your marketplace item. You can indeed have linked templates in the main template, but ensure you only have one entry in the manifest.json file.
Here are some detailed blog posts that walk one through the process of creating and publishing a custom Azure Stack Hub Marketplace item:
Adding a Marketplace Item to Azure Stack
Adding and Using OS Gallery Items to Azure Stack TP2
Adding and Using DSC for Linux Gallery Item to Azure Stack TP2
Related
I want to add a custom tab in the Azure DevOps build results page, next to the Summary tab.
Exactly the same questions were asked by different users in 2019. But the sample repo shared is outdated and never updated for more than 5 years.
https://github.com/microsoft/vsts-extension-samples/tree/master/build-results-enhancer
What is the extension points to be used for the same?
All other searches point to the same old repo.
Azure DevOps add custom Tab to Build Summary
Check out the newest documentation on extension development using the Azure DevOps Extension SDK. The new Azure DevOps extension sample uses a new Azure DevOps SDK along with the React-based components in the Azure DevOps UI library described in this site.
I am following along the tutorial with SmartHotel360 and trying to set it up. In the README.md, it says 'In VSTS, navigate to Services by clicking on the gear icon...' and this is to create a new service endpoint. Where is this done? What is VSTS? Visual Studio Team Server? Do I first make a branch of the SmartHotel360 and open this in Visual Studio? What if I am using one email account to access the code where the tasks are assigned and another email to complete the courses? Does this make a difference?
I guess my question is, where is this VSTS? Is this where I view the SmartHotel360 code?
Azure DevOps Services was formerly named Visual Studio Team Services (VSTS) -- rebranded as Azure DevOps in 2018. So the tutorial you followed should be before 2018.
The github README.md about SmartHotel360(like this) are retired, archived, and no longer supported. For the latest sample references please visit: https://aka.ms/tailwindtraders & https://aka.ms/rpsls
To interact with Azure, you'll need to create a Service Endpoint in Azure DevOps. This endpoint includes the authentication information required to deploy to Azure. This document gives a guide to configure Service Endpoint in Azure DevOps, please refer to it.
I'm writing a dashboard widget for an Azure Devops dashboard, and I'm finding the cycle of modify-publish-refresh dashboard-set breakpoints in Chrome tools-refresh page again to be rather tedious.
Is there a way to test or debug a dashboard widget directly within Visual Studio or VS Code?
I'm using Add a dashboard widget as a starting template for my widget - happy to change though!
You can develop locally. Since Azure DevOps uses an iframe to show your extension's content, you can run a local server and reference that in the vss-extension.json manifest.
By default, when you launch the Developer Tools, the Developer Console is in the context if the primary page, or the top window. In other words, you're able to access the top window's DOM and state. Use the "Target" dropdown (shown above) to switch the context to your extension's frame. You are now able to access the DOM and global state of your extension's frame.
Besides, you could also use an official extension Azure DevOps Extension Hot Reload and Debug.
This repository demonstrates how to load an Azure DevOps extension's
code directly from the dev machine rather than bundle all the code and
deploy it through the marketplace. We will leverage the (somewhat
hidden) capability in Azure DevOps to load content from localhost,
which will enable us to use hot reload and debug in VS Code.
More detail info and ways, please kindly refer below links:
Debug a web extension
How to debug VSTS extension build summary tab without deploying to VSTS service?
How to debug and develop Azure DevOps extension without deployment?
I am doing some research for Powerapps integration with Azure DevOps.
However there is limitated information for it.
It is possible to integrate powerapps inside a Task for AzureDevops?
Based on, that we have a .zip file with the Powerapp, and we want to create a Build and Release/Deploy for several environments.
Thank You.
It is possible to integrate powerapps inside a Task for AzureDevops?
Yes it is.
You can leverage the Solution concept of the Microsoft Power Platform and the Power Apps BuildTools (preview) extension for Azure DevOps.
Update 11/2020: This is now GA and called Power Platform Build Tools
I've written a complete step-by-step guide on this topic:
A Continuous Delivery Approach for No-Code Solutions in Microsoft’s Power Platform
Bottom line:
With this build tool, you can automatically check-in a Solution into source control and deploy it using a continuous delivery approach with the help of Azure DevOps. See the screenshot for a sample configuration of the Export and Import Solution Task.
It works for everything you can organize inside a Solution, e.g.:
Power Apps
Power Automate Flows
AI Builder Models
Common Data Service Entities
It is possible to integrate powerapps inside a Task for AzureDevops?
I am afraid there is no such Task integrate powerapps for AzureDevops at this moment.
If you want to integrate powerapps with azure devops, you can follow the guide step by step:
Microsoft Teams – Integration with Visual Studio Team Services using PowerApps.
Besides, AFAIK, PowerApps should not be "Build/Deployed" through Azure Devops.
When you are developing with PowerApps, there is no way to do Source
Control. There are no source files. The only artifact you can version
control is the .zip file that you can export.
And
In PowerApps, you don’t have to build your code. Any change you make
to the application is live for you to test it. In that way it is very
productive. To publish the application you just click on the publish
button and it is live.
Check this great blog: PowerApps From A DevOps Perspective for some more details.
Hope this helps.
Solutions are a way to package your components in a single zip file and use Powerapps build tools to import your solution on to a different environment or tenant.
It is still a an improvement from manually importing each app or environment variable and then import it on to target system, but it lacks what we call as automation of deployment.
To provide an eg, I will explain what I have done, and what still constitutes of a manual task:
I created an enterprise level app using powerapp canvas model. My app consumes data from around 20 APIs. These API calls are implemented in power automate.
We have 4 environments, dev, sit, uat and prod. Now I cant keep on importing flows in each environment and change their api URLs to point to the deployed environment. So I used environment variables for each environment which stores api URLs for each environment. This can be done under solution.
Under the same solution, I added my app. So now my solution has 2 things, my app and the environment variable which consists of api URLs.
I then use powerapps build tools to move this solution from dev to sit.
Steps: use build tools tasks to perform the following
Export solution
Unpack it in git
Pack it
Import the solution.
This successfully moves my solution to sit.
But the solution environment variable still points to the dev url.
So I have to override environment variables to store sit URLs.
This manual intervention to edit environment variable is as good as doing all the tasks manually.
This was the case when PowerApps was first announced; however, this is no longer the case.
While it is technically true that there is no actual code that would be managed and deployed with a PowerApp or Flow but that doesn't mean that you can not use the power of Azure DevOps. Additionally, when creating a PowerApp / flow you would also be creating entities and even Model Driven apps - and these uses solutions - which naturally work well to deplooy within Azure DevOps.
Microsoft is building out this whole construct to enable all these to deploy...
While the whole incorporation of PowerApps and flows into Solutions is not fully baked yet - they are targeting to have this ready around the October time frame this year.
We have been talking to Microsoft about also enabling PowerApps and flows to follow the same expansion that solutions do so that they can take advantage of the full branching strategy.
So even though you would be simply exporting out zip files into your repo - you can still take advantage of the full devops pipeline which is highly recommended.
Use this component, it still on preview mode but is working fine on my side
https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerApps-BuildTools
I need to customise vsts build summary by adding a chart(a pie chart and a bar chart) for which the data source will be azure blob or a local csv file generated after the build execution.
Do we have any default vsts tasks available or
writing vsts extensions is the only way out of this.
There is not any built-in official task or extension could achieve your needs. You could go through Visual Studio Team Services Marketplace if there are some 3rd-party extension meet your requirement.
You want to build an extension for VSTS and Microsoft has created a GitHub repo with a number of samples and reading material to get you started. Otherwise, you may have to write your own extension, some tutorials for your reference:
VSTS Extensions Samples
Develop Extensions for VSTS
As for how to accessing Azure Storage from a VSTS extension, take a look at this blog.