If you have a OneAtlas subscription that you want to use on the UP42 Platform, you need to have the OneAtlas credentials to create an environment and than add the OneAtlas API key-value pair as an environment variable. To connect the environment with the UP42 Platform and use your subscription, you then need to reference it in the relevant blocks that are included in your workflow(s).
If you already have a OneAtlas API key, we recommend generating a new one just for using it with UP42. This way, you can manage it separately from your other API key(s).
For completeness sake, we also included the step for generating a new OneAtlas key. Since OneAtlas is an external service, please note that we cannot guarantee the accuracy of the information herein provided.
Login to your OneAtlas account.
Go to your API key listing page here.
Create a new API key and copy the value.
The API key is only displayed once. If you fail to copy and save the value in a separate file, it will be lost and you will need to generate a new API key. Use only temporary storage for this purpose, your own secret storage or any other secure storage system.
In the console, open the tab workspace.
Click on tab Environments.
Scroll down and click on the button Create Environment.
Type in the name of your environment (in this example: OneAtlas LL) and click Save.
You now created an empty environment.
Go to your environment and click on Add Environment Variable.
Add the name
Copy the OneAtlas API key and paste it into Value, then click Save.
Your newly created environment variable
ONEATLAS_API_KEYshould now be visible on your Environments dashboard.
You can add as many environment variables as you want, but make sure their names are unique. For using OneAtlas data, please name the environment variable
ONEATLAS_API_KEY, otherwise the credentials pass-through fails.
Please note that you cannot change the values of the environment variables. If you need to change the value of a variable, you need to create a new environment and add the variable with the respective changed value there.
Go to your project.
Open the workflow where you want to enable the OneAtlas credentials pass-through.
Reference the environment in the relevant block(s). In the case of a data subscription such as OneAtlas, the environment should be referenced in the data block.
Configure the job. For more information, please refer to Job Configuration.
Run the job.
After the job has been successfully run, you can go to the job dashboard and check the credit consumption for each step. Since you referenced the previously created environment in the data block, the credential pass-through enables you to consume OneAtlas data without any credit costs. The first step will display a negligible amount of credits solely used for infrastructure.
Congratulations! You successfully ran jobs without getting charged by UP42 for the data retrieved through your OneAtlas subscription.