Access to own storage using aio-lib-state and aio-lib-action failed | Community
Skip to main content
Urs_Boller
Community Advisor
Community Advisor
September 9, 2020
Solved

Access to own storage using aio-lib-state and aio-lib-action failed

  • September 9, 2020
  • 1 reply
  • 2981 views

To have a local storage during development on own environment (see https://experienceleaguecommunities.adobe.com/t5/project-firefly-questions/aio-local-action-with-error-on-aio-lib-state-init-and-put/qaq-p/377022) I thought I could use my access to Azure and setup containers to be used in the sdk init.
But aio-lib-lifes failed with error like "request to url XXX failed - getaddrinfo EAI_AGAIN" and aio-lib-files succeded but I was not able to write any keys...

is there any documentation on how to setup MS Azure to handle aio-lib-files and aio-lib-state? is it possible to use this access when running the "aio app run --local"? thanks for any help in this case!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by duynguyen_adobe

Hi @urs_boller , I managed to init the State SDK and write / read operations with this.

const state = await stateLib.init({ cosmos: { endpoint, masterKey, databaseId, containerId, partitionKey } })

My "endpoint" value is like https://<tenant-name>.documents.azure.com:443.

Do you have the same?

1 reply

duynguyen_adobeAdobe EmployeeAccepted solution
Adobe Employee
September 9, 2020

Hi @urs_boller , I managed to init the State SDK and write / read operations with this.

const state = await stateLib.init({ cosmos: { endpoint, masterKey, databaseId, containerId, partitionKey } })

My "endpoint" value is like https://<tenant-name>.documents.azure.com:443.

Do you have the same?

Adobe Employee
September 10, 2020
Thanks for confirming, Urs. Great to hear!