Multiple Provisioning profiles for iOS azure build pipeline - azure

I am unable to build our app which having multiple provisioning profiles like IntentExtension and IntentExtensionUI .

Currently there's no support of multiple provisioning profiles for Xcode task (for example for iOS App Extension). You could check this doc: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/build/xcode?view=azure-devops#using-multiple-provisioning-profiles
As a work around, you need an "exportOptions.plist". This allows you to include multiple schemes and their associated provisioning profiles (eg. if you have a Today Widget or Intents as well as your main project).
Refer to this for details: https://github.com/Microsoft/azure-pipelines-tasks/issues/8811

Related

Ability to onboard custom Ibiza Extensions

Currently based on https://github.com/Azure/portaldocs custom Azure Blades can only be developed internally within Microsoft Product Groups, however they are using React Templates to provide a customized view for custom resources. Ibiza Extensions (Codename for the Portal) would be a great extension on top of custom resource providers.
Is there any capability to onboard resources from organizations, which published their service through the marketplace and/or partners after going through the official onboarding process?
I've checked through the https://github.com/Azure/portaldocs documentation to understand the process and details on how to get engaged. The repository however does not intake any issues to ask there.
Currently we don't have any plans around extension development in our roadmap in the near future. In general, we would prioritize against existing backlog, add in roadmap as appropriate and would announce and/or update the related Azure document once any feature request is addressed.

Link a dialogflow agent to a Google Cloud Console project and inherit all the team members i assigned to the project?

How can i create a dialogflow agent and associate it with the Google Cloud Console project i created and have it inherit all the team members i assigned to the project ?
I am working on a dialogflow project. I created a new project in the Google Cloud Console and added some team members. However when i switch to the dialogflow console i do not see my project and the people i added to it. when i create a new agent in dialogflow it seems to have nothing to do with the project i created in the cloud console and i have to explicitly share the agent with the team. So the Google Cloud Console project is sort of useless.
For example in Azure cognitive services i can link everything to my root project.
Best CK
Google could do better in making these resources (e.g. Projects) more clear.
Actually (to my knowledge) all Google Projects represent the same underlying project resource and you can e.g. view DialogFlow projects from Google Cloud Console and vice versa.
I suspect (!) that you created 2 different projects: one using (Google Cloud Platform) Console and one using DialogFlow Console
If you have the Cloud SDK (aka gcloud) installed, you should be able to list all your projects (Cloud, DialogFlow etc.) using:
gcloud projects list
Now, to answer your question. Users of Google (!) Projects are Google accounts users and groups and also include service accounts. You may list the users for a given project with:
gcloud projects get-iam-policy ${PROJECT}
Ideally, what you want to do is ensure that this policy is reflected across both projects. I'm reluctant to provide a script because service accounts complicate this sharing. Service accounts work across projects but they are created automatically in projects. A simple copy-and-paste of accounts may break something for you.
That said, here's a gcloud command to enumerate the list of ${ROLE} (roles/owner) from one project ${SRC}:
PSRC=...
ROLE="roles/owner"
MEMBERS=$(gcloud projects get-iam-policy ${PSRC} \
--flatten=bindings \
--filter=bindings.role:${ROLE} \
--format="value(bindings.members)") && echo ${MEMBERS}
NB There's probably a way to split user:some#email.com if you need to
You could then iterate over this list and add (!) these accounts to ${PDST}
for MEMBER in ${MEMBERS}
do
gcloud projects add-iam-policy-binding ${DST} \
--member=${MEMBER} \
--role=${ROLE}
done
Lastly, when you create a DialogFlow project you are provided with the option to use an existing Google (Cloud) Project. Next time, you follow this flow, please look for the "create new or use existing project" prompt. You would be able to select the Project you'd created previously to reuse your users.

How to separate Development and Production environment on Azure API management?

I am developing an application using microservice-based architecture. I Know that on Azure API management we can register our APIs. Now the problem I am facing is that my micro-services(development and production ) are deployed on AKS(Azure Kubernetes Service) and both have different IP Addresses as provided by the AKS. How do I differentiate between the two environments so that my front end team has two separate URLs for development and production? The base URI of the API Gateway on azure is pre-configured and cannot be changed, how do I get two URLs?
My main concern is do I need to create two instances of Azure API Management Service?
Have you checked Azure API Management DevOps Resource Kit . As recommended, yes you need to create two instances for your environments and deploy using ARM templates
If you don't want to create several instances, you might also try using versions and revisions.
Revisions
You can create revisions by right-clicking an API and tap "Add revision".
The revision can be accessed via the rev=2 url specifier as shown in the picture above. After successful testing, you can easily set a revision to be the "current" API, which won't need a revision specifier anymore.
Versions
You can create a version by right-clicking an API and tap "Add version".
In the "Versioning scheme" dropdown, you can also choose how the version should be specified. The options are:
Path
Query string
Header
so you can target each version separately.

How to enable/disable project services through API

I am migrating from TFS 2015 to Azure DevOps. The process of creating the target project and importing the old git repository can easily be done through the Azure DevOps API.
But each new project, either created manually or by API has always all services (Boards, Pipelines, Test Lab, ...) enabled. Is there a way to change the default setting of which services should be enabled on new projects? Or even better an API method to switch certain services on / off?
We have hunderets of projects and therefor it's not feasible to open each project in the browser, change to the project settings page and adjust the services.
I haven't found anything in the docs: https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-5.0
This guy wrote a blog post on how to do this
This is an excerpt pulled from his post:
PATCH https://{account}.visualstudio.com/_apis/FeatureManagement/FeatureStates/host/project/{project-id}/{feature-id}?api-version='4.1-preview.1'
content-type: application/json
{"featureId":"{feature-id}","scope":{"settingScope":"project","userScoped":false},"state":0}
Replace account,project-id and feature-id as appropriate. Here are the feature id’s I know of.
ms.vss-build.pipelines [Azure Pipelines]
ms.vss-test-web.test [Test Plans]
ms.vss-work.agile [Azure Boards]
ms.vss-code.version-control [Azure Repos]
ms.feed.feed [Azure Artifacts]
It looks like turning a service off really just means hiding it from the UI.
Edit: it looks like the .net SDK has built in support for this as well

Web app onboarding to Azure Web Marketplace

We checked this documentation - https://blogs.msdn.microsoft.com/appserviceteam/2016/08/26/onboarding-to-azure-web-marketplace on how to onboard our web apps in the Azure marketplace and also the GitHub link - https://github.com/SunBuild/web-app-marketplace
We have contacted MSFT on how to host our application which has an API and WCF applications as sub-applications.
MSFT replied that sub applications are not currently supported in through this onboarding model.
So, we are trying to onboard the three applications individually and link them in the Azure marketplace. We are not sure whether this will work or if this is possible.
In the sample applications in the GitHub link - https://github.com/SunBuild/web-app-marketplace, they have a hosting plan JSON file for the web app resource. Can we link the applications using this hosting plan JSON file?
We could not find any information or definition related to this hosting plan file - https://github.com/SunBuild/web-app-marketplace/blob/master/WebApp-SQLDatabase/DeploymentTemplates/Website_NewHostingPlan_SQL_NewDB-Default.json
Does anyone tried this before or know how to do this?
sub applications are not currently supported in through this onboarding model.
From the documentation, we could know if web app need Virtual application setting to be configured for web app, we will not be able to on board the application.
we are trying to onboard the three applications individually and link them in the Azure marketplace. We are not sure whether this will work or if this is possible.
In my view, if you on board these application individually, it may not enable us to bundle multi individual applications to make them link with each other. You could contact with Azure marketplace support team.
We could not find any information or definition related to this hosting plan file - https://github.com/SunBuild/web-app-marketplace/blob/master/WebApp-SQLDatabase/DeploymentTemplates/Website_NewHostingPlan_SQL_NewDB-Default.json
In the link you posted, we could find that it is an Azure Resource Manager (ARM) template that is used to define resources you want to deploy. This article explained about the Azure Resource Manager template, please refer to it.

Resources