We are authoring Azure Resource Manager templates. We are using the following deployment template schema, because it is the one that we saw in an example.
http://schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json#
It is from early 2014. Where can we find a list of more recent schema versions?
We have looked at the list of resource Manager providers, regions, API versions and schemas. It references a schema for each provider not for the entire template.
When we do find a list of more recent schema, how do we evaluate which deployment template schema to use? Is more recent better?
Here is our current hack:
Go to https://github.com/Azure/azure-resource-manager-schemas
Press t to enter the [GitHub File Finder][3].
Type DeploymentTemplate.
Voila. We have a list of deployment template schema, which displays two API versions.
More recent is better. But in general you should be able to stick with the top level schema of:
http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#
That will pull in the proper version of all the child schemas. We update the child schemas so all your existing templates don't have to be updated. Multiple API versions are supported in the child schemas to support "backward compat".
If you do peruse GH, look at the readme.md (that tells you what to test and therefore what's in use) and the file you want to watch is:
https://github.com/Azure/azure-resource-manager-schemas/blob/master/schemas/2015-01-01/deploymentTemplate.json
As that's the top level schema file.
Still no official list in 2020, until we found one, here's the current root schemas for quick reference
Resource group:
https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#
https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#
https://schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json#
Subscription:
https://schema.management.azure.com/schemas/2018-05-01/subscriptionDeploymentTemplate.json#
Management Group:
https://schema.management.azure.com/schemas/2019-08-01/managementGroupDeploymentTemplate.json#
Tenant:
https://schema.management.azure.com/schemas/2019-08-01/tenantDeploymentTemplate.json#
This will definitely be outdated in the future, this is sourced from here so be sure to check too if you want the latest. Feel free to update the list in the future.
I was searching for same answer, found this question.
Sorry for all those who answered before, i wasn't satisfied with the proposed solutions.
So i found another way, maybe this is suitable :)
At this page https://learn.microsoft.com/en-us/azure/templates/
you'll find on the left side a list of all types of resources that can be defined in an ARM template.
For each resource (e.g. CosmosDB) you'll find a link with All resources (e.g. https://learn.microsoft.com/en-us/azure/templates/microsoft.documentdb/allversions for CosmosDB) which lists all versions for that resource.
Hope it helps!
p.s.: also there's the link of Latest (e.g. for CosmosDB https://learn.microsoft.com/en-us/azure/templates/microsoft.documentdb/databaseaccounts) which gives the latest format of that resource ;)
Related
All
I'd like to create some project release versions(released and unreleased). In JIRA, you can find these versions in following JSON file. I need these versions to associate with work items in Azure boards. For example, to show a work item (Type: Bug) is found in certain version. My project is not built on Azure pipeline, So I don't have any release pipeline, so Is there any way to define these versions and name them with whatever name I want. Thanks.
https://jira.XXXX.com/rest/api/latest/project/XXXXX/versions
Currently, we seem have no method to directly link work items on Azure Boards to the 3rd-party CI/CD pipelines. Only Azure Pipelines is supported.
As a workaround, you can try to add a custom field on the work item to show the related release as the field value.
For example, add a text field named "Release" on the Bug item, then you can fill this field with the release version or the URL of the related release.
In the 3rd-party CI/CD pipelines, you can set up a step to execute the REST API "Work Items - Update" to automatically fill the release version in the field.
I want to get a list of all the variables (optional or not) and ideally their defaults defined in a resource. Say in the AWS provider, but need anything. I know I can get and look at the documentation (which doesn't list everything I want) or the raw provider code and find all this, but is there a utility that would list this for me?
The schemas-extractor from the Hashicorp Terraform / HCL Language plugin source builds a machine readable schema document for all providers in the terraform-providers org on GitHub.
The Terraform LSP is another likely source of this information.
How to transfer the repository or a whole set of repositories from one gitlab group to another subgroup. For example companyname.gitlab.com/team one/. To gitlab.com/team_first/phase1/
The repositories/projects themselves still need to be exported by API, one by one.
But the new "Group Import/Export " feature from GitLab 13.0 (May 2020) can be a welcome addition.
Export and Import Groups in the UI
Previously, users could only migrate groups by using the Export/Import API to create an Export file, then using the API a second time to upload the file to the target instance.
As a first step toward a more frictionless solution, we have enabled Group Export in the GitLab UI.
We plan to introduce similar Import functionality to the UI within the next few weeks.
See documentation, issue and Epic.
See GitLab 14.2 (August 2021)
Group Migration achieves parity with group import/export
The new GitLab Migration feature can now migrate an entire group with all its subgroups and related data. The data migrated includes everything contained in group exports, making this a much easier way to migrate entire groups.
The pre-existing group import/export is a two-step process that requires exporting a file and then importing it into another GitLab instance.
Now, users can initiate a group migration with a single click. Migration also includes all the subgroups and their data, which previously required separate export and import processes for each subgroup.
See Documentation and Epic.
See GitLab 15.6 (November 2022)
Associate MRs to issues when migrating groups with projects
When migrating groups using GitLab Migration, GitLab now preserves associations of imported merge requests to issues.
This populates the Related merge requests section
on the issue details page.
See Documentation and Issue.
We are building a custom Visual Studio build task to implement compliance validation of the builds defined by our developper teams.
The objective is to mark builds using "unauthorized" tasks, or failing to use mandatory tasks in a way that will be possible for a BuildCompleted servicehook to act upon later on.
We are creating a JSON structure describing the different business rules we want to enforce, and we have a service hook catching end-of-build events to create a tracability file that will mark the build artifacts as "deployable" or not.
I can see from the MS references that a Issue collection is returned with the GetBuildDetails responss that seems to list exactly the kind of information we'd like to pass along.
Anyone found a way to populate that property?
Thanks!
The solution is add additional information to the build result by using Logging Commands (e.g. ##vso[task.logissue]error/warning message)
I am trying to find a way to search multiple project's code in gitlab CE.
Has anyone encountered this before, or have a recommended approach?
(I realize that if this is even possible, then I would likely need to create a script that mimics the current call from the GUI multiple times and combine the results. )
Recently came into a similar need. My particular use case is a self-hosted instance of GitLab CE. Seems like it's possible to use GitLab's API where the scope is limited to snippet, then loop through your groups and projects.
Example code:
https:// (instance_server) /search?utf8=%E2%9C%93&snippets=&scope=&search= (key words) &group_id=22&project_id=81
Other links:
GitLab's paid version.
https://docs.gitlab.com/ee/user/search/advanced_search_syntax.html#syntax-search-filters
Mention of original request (closed)
https://gitlab.com/gitlab-org/gitlab-ce/issues/14597
https://forum.gitlab.com/t/search-code-across-all-projects/2263 (SourceGraph)
You can create a Group, migrate or move all of the projects you want to search to that group, and then search just that group.