-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use cloud backed url #57
Comments
Create a unique storage account name. Ie. window version, featue pack, build number to distinguish between various storages. |
|
sorry yeah also take into account that you would need to create the blob storage according to (change the name, need to parameterize that https://github.com/adrianriobo/qenvs/blob/059ac80a7b6fc22879492f6b05cd6f071390f447/hacks/azure_setup.sh#L18 also take into account last line you need the |
Also I am doing it for some other project so I found out there is one cmd missing on the script redhat-developer/mapt#185 The cmd will create the blob container for the storage so lets say you create it with
then on your podman run you will have something like: ...
--backed-url azblob://qenvs-state/${storage_id} \
... and 2 envs: ...
-e AZURE_STORAGE_ACCOUNT='${{ secrets.AZURE_STORAGE_ACCOUNT }}' \
-e AZURE_STORAGE_KEY='${{ secrets.AZURE_STORAGE_KEY }}'
... |
Qenvs offers the feature to store the state on an external resource, for windows environments we will use https://www.pulumi.com/docs/concepts/state/#azure-blob-storage
This willl allow us to setup a scheduled cleaner to check states on that storage and ensure no running instances
The text was updated successfully, but these errors were encountered: