Fix: How to move blob from one storage account to another using logic app

 To move a Blob from one Azure Storage account to another using Azure Logic App, you can use the built-in Azure Blob Storage connectors. Here's a step-by-step guide:


**Prerequisites:**

1. Azure Logic App: Create an Azure Logic App if you haven't already.

2. Azure Storage Accounts: Have the source and destination Azure Storage accounts set up and accessible.


**Step 1: Create a Logic App**


1. In the Azure Portal, go to your Logic App's resource group and create a new Logic App if you don't have one already.


**Step 2: Create a Trigger**


1. In your Logic App designer, select a trigger to start your workflow. For this example, you can use the "When a blob is added or modified (properties only)" trigger from the Azure Blob Storage connector. This trigger will start your workflow when a new blob is added or modified in the source storage account.


**Step 3: Add an Action for Copying the Blob**


1. After the trigger, add a new action by clicking the "+" sign below the trigger.


2. Search for "Azure Blob Storage" in the search box, and select "Azure Blob Storage" from the list of connectors.


3. Choose the "Copy blob" action. This action will copy the blob from the source storage account to the destination storage account.


4. Sign in with your Azure account and select the source storage account and container.


5. In the Destination section, choose the destination storage account, container, and specify the name of the destination blob. You can use dynamic content to select the blob name from the trigger.


**Step 4: Handle Errors**


1. It's a good practice to handle errors in your workflow. Add a condition or other actions to handle potential errors that may occur during the copying process.


**Step 5: Save and Test**


1. Save your Logic App and test it by adding or modifying a blob in the source storage account. Verify that the blob is copied to the destination storage account.


**Step 6: Monitoring and Scheduling**


1. You can set up monitoring, scheduling, or other triggers as needed to automate the copying process. For example, you can trigger the workflow at specific intervals or based on specific conditions.


This Logic App will automatically copy blobs from one storage account to another whenever new blobs are added or modified in the source account.


Please note that additional settings, such as authentication and security, may be required based on your specific use case and security requirements. Ensure that your Logic App and storage accounts are appropriately secured and configured to meet your organization's needs.

Comments

Post a Comment

Popular posts from this blog

bad character U+002D '-' in my helm template

 In Helm templates, the hyphen character (`-`) can sometimes be treated as a reserved character, particularly when defining values or labels. To include a hyphen character in a Helm template without issues, you can use one of the following approaches: 1. **Quoting the Hyphen:**    You can enclose the hyphen in double quotes, like this:    ```yaml    key: "-"    ```    This way, Helm will interpret the hyphen as a string rather than an operator. 2. **Using Backticks:**    If you need to use the hyphen within a Go template function or inside backticks, you can escape it with a backslash (`\`), like this:    ```yaml    value: `{{ .Values.someField | printf "%s \\-" }}`    ```    The backslash prevents Helm from interpreting the hyphen as a special character. 3. **Variable Assignment:**    Assign the value to a variable and use it. For example:    ```yaml    {{- $hyphen := "-" }}    key: {{ $hyphen }}    ```    This way, you can use the variable `$hyphen` wher
Read more

GitLab pipeline stopped working with invalid yaml error

 When your GitLab pipeline has stopped working with an "invalid YAML" error, it means there's a problem with your `.gitlab-ci.yml` file. This could be due to syntax errors, incorrect indentation, or other issues in your pipeline configuration. Here's how to troubleshoot and resolve this issue: 1. **Check for Syntax Errors**:    Carefully review your `.gitlab-ci.yml` file for any syntax errors. Common issues include missing colons, indentation problems, or mismatched quotation marks. Use a YAML linter or an online YAML validator to identify and correct syntax errors. 2. **Indentation**:    YAML relies heavily on proper indentation. Make sure that all lines within the same block have consistent indentation (typically using spaces, not tabs). Incorrect indentation can cause YAML parsing errors. 3. **Dashes and Lists**:    Ensure that you use the correct syntax for lists (arrays) in YAML by starting each item with a dash (`-`). Be consistent with your use of dashes throug
Read more

How do I add a printer in OpenSUSE which is being shared by a CUPS print server?

 To add a printer in openSUSE that is being shared by a CUPS print server, you can use the following steps: 1. **Ensure CUPS Client is Installed:**    Make sure your openSUSE system has the CUPS client tools installed. You can install them using the following command:    ```bash    sudo zypper install cups-client    ``` 2. **Discover Available Printers:**    Use the `lpinfo` command to discover available printers on your CUPS print server. Replace `cups-server-hostname` with the hostname or IP address of your CUPS server:    ```bash    lpinfo -v -h cups-server-hostname:631    ```    This command should list the printers shared by the CUPS server. 3. **Add a Printer:**    Use the `lpadmin` command to add a printer. Replace `printer-name` with the name of the printer you want to add and `printer-uri` with the URI obtained from the `lpinfo` command:    ```bash    sudo lpadmin -p printer-name -E -v printer-uri    ```    For example:    ```bash    sudo lpadmin -p MyPrinter -E -v socket://cu
Read more