Valeriy Zabawski

After applying patch from the PR #249, it works. ``` cd "/tmp/git-crypt-${VERSION}" && \ curl -L https://patch-diff.githubusercontent.com/raw/AGWA/git-crypt/pull/249.patch | git apply -v ```

Btw, there are still some deprecation warnings left after applying the patch, but they do not break the build. ``` crypto-openssl-11.cpp: In constructor 'Aes_ecb_encryptor::Aes_ecb_encryptor(const unsigned char*)': crypto-openssl-11.cpp:58:32: warning: 'int AES_set_encrypt_key(const...

To summarize, I see this issue as a mix of factors: - Configuration on my side was incorrect. - AzureRM provider didn't handle this case and submitted incorrect configuration to...

I fixed this issue by specifying `resourceGroup` where storage account is located under `config` section. After that the location was marked as available. It might be a defect in the...

This issue affects me too. In my case, I have dynatrace-operator chart which automatically installs CRDs using its internal CRD management mechanism implemented in dynatrace-operator itself. What I'm trying to...

Thank you for your reply. I'll wait for the new release since this behavior rarely bothers me. :)