I am trying to replicate the artifacts between two jfrog artifactories. But here we don't want to do it from the UI, can we replicate the artifacts by using curl or jfrog rt commands.
Ref:https://www.jfrog.com/confluence/display/RTF/Repository+Replication#RepositoryReplication-WatchtheScreencast
Yes and no, and I'll explain. You can trigger, using the REST API, an existing replication, meaning that you already configured all of the required parameters for the replication on the repository.
You can't run a replication between two instances of Artifactory if you don't have it set up already, meaning if the repository doesn't have replication configuration, you will not be able to replicate from it.
Also, the jfrog cli will not be able to assist you in this specific scenario.
Related
I am using repos for Azure DevOps to connect Azure databricks to my respositories in DevOps. I need to pull automatically from Azure DevOps pipelines. For that I tried using databricks API to pull, but referring to this link there is no method for pulling.
Following the instruction and looking at swagger the only methods available are:
Is there a way to pull via API or CLI or any other way programmatically? If yes, how?
You need to use PATCH endpoint as described in documentation. It will Updates the repo to the given branch (or tag) - if you already on the given branch, then it will pull the latest changes. You can also use databricks-cli for that, like, it's shown in the following demo.
I have a newly created ADF and I will have to configure the repository with the ADF. I have almost 100 count pipelines, their related datasets, linked services, triggers in the repository. How can I load all the pipelines and their respective into the ADF. Once I configure the git with the ADF I am unable to see the pipelines. Any thoughts?
Did you select the below option when configuring the repo?
If yes double check the Root folder path. If it's not set accurately you will not be able to see pipelines, dataset etc.
I followed the steps below to configure GitHub repo in ADF. Please make sure you also followed the same steps.
Enter name of GitHub repository owner. After this you will be redirected to login page of GitHub.
Authoring directly with the Data Factory service is disabled in the
Azure Data Factory UX when a Git repository is configured. Changes
made via PowerShell or an SDK are published directly to the Data
Factory service, and are not entered into Git.
Select your repository and fill required details.
You will get all Pipelines and Datasets as shown in below screenshot.
For more information follow GitHub integration best practices
I currently have an application in amplify but I want to integrate the repo, but I have it in azure, I don't see the option to integrate directly with azure from amplify.
In your case, the best suggestion would be to use multiple remotes provided by GitHub. no need to worry if you are not using GitHub because the process and the commands are the same.
As you are using 2 different environments you need to use Azure Repos and Code commit with git standard.
Once you have done setting multiple repos, configuring CI/CD pipeline would be a better process to deploy based on your push.
It's worth pointing out that you’ll need to properly setup and configure your CI/CD pipeline. AWS provides a number of services to support this including AWS CodePipeline, AWS CodeBuild, and AWS CodeDeploy.
We configured Azure Api Management and as part of it the Azure Repository where it should sync its configuration to.
Unfortunately we selected the wrong repository. Now we are unable to switch the Repository as any option for doing it is missing in the Api Management.How to change the repository in Api Management?Thanks for any advise
It was a misunderstanding on my part. Everything works as described in the Microsoft documentation. I meant the repository of Apim is the one we have to set up in Git/Tfs, which is of course not so. Apim has its own repository and we can use for example powershell to read the data from that repository and upload it to our own repository or vice versa.
We have multiple teams working on the same Api Management instance, and the current git-based configuration that API Management provides, does not really facilitate a good process for us (with support for code reviews, pull requests, deploys etc.).
Can we use a GIT repository in Azure DevOps to control the configuration instead of having to use the repository provided directly by API Management?
Our primary use cases are:
Merge/sync changes from API Management into our central repository
Performing changes in a DevOps repo in separate branches, merge the changes to the main branch via pull requests and sync'ing the changes to API Management
We can clone the configuration repository and push changes back- using our familiar Git commands.
You can try to run the following command in cmd task of azure devops pipeline.
git clone https://username:password#{name}.scm.azure-api.net/
git add .
git commit -m "abc"
git push
Here are the document and similar case you can refer to.