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
Currently, the storage account secret displays as the following when doing a k get secret
10471 ± k get secret
NAME TYPE DATA AGE 5 96m
storageaccount-rg-expotest-dev-saexpotestdev Opaque 5 93m
erins-MBP ॐ ~/go/src/github.com/frodopwns/exposure-notifications-server/examples/aso-dev-deploy:(18h1m|git@chartdraft!)
10472 ± k get storageaccount
NAME PROVISIONED MESSAGE
saexpotestdev true successfully provisioned
We should rename the secret storageaccount-rg-expotest-dev-saexpotestdev to the standard naming convention across controllers for secrets, or something more declarative.
Done criteria
Rename the name of the storage account secret to the standard naming convention across containers.
For eg. After this task is done, the user should be able to use either webhooks or the declarative model for K8s
User story reference
#
The text was updated successfully, but these errors were encountered:
Currently, the storage account secret displays as the following when doing a
k get secret
We should rename the secret
storageaccount-rg-expotest-dev-saexpotestdev
to the standard naming convention across controllers for secrets, or something more declarative.Done criteria
Rename the name of the storage account secret to the standard naming convention across containers.
User story reference
#
The text was updated successfully, but these errors were encountered: