You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Values and examples in the document for using Azure Blob artifact repository does not reflect AzureArtifiactRepository. Following the document/examples leads to following error in the argo workflow controller: Failed to register watch for controller config map: error unmarshaling JSON: while decoding JSON: json: unknown field \"blob\ in the workflow controller
...
artifactRepository:
azure:
endpoint: https://myblob.blob.core.windows.netcontainer: mycontainerblob: myblob # this should be blobNameFormataccountKeySecret:
name: my-azure-storage-credentialskey: my-account-access-key
jsong336
changed the title
Argo Workflow not reflecting AzureArtifiactRepository blobNameFormat
Artifact Repository for Azure Blob - values/examples not reflecting AzureArtifiactRepository blobNameFormat
Aug 3, 2023
Describe the bug
Values and examples in the document for using Azure Blob artifact repository does not reflect AzureArtifiactRepository. Following the document/examples leads to following error in the argo workflow controller:
Failed to register watch for controller config map: error unmarshaling JSON: while decoding JSON: json: unknown field \"blob\ in the workflow controller
This started happening after upgrading to 0.32.1 but was in several version behind before upgrading. I am assuming this might have started complaining after https://github.com/argoproj/argo-workflows/blob/master/docs/upgrading.md#feat-fail-on-invalid-config-8295
Passing in
blobNameFormat
instead ofblob
seems to workRelated helm chart
argo-workflows
Helm chart version
0.32.1
To Reproduce
Install Argo Workflow with Chart 0.32.1 and use azure artifactRepository with
blob
keyExpected behavior
This is probably expected behavior but will requires update in document
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: