pýrus
pýrus
If this makes sense I started locally with a draft: ```diff diff --git a/pkg/apis/ceph.rook.io/v1/types.go b/pkg/apis/ceph.rook.io/v1/types.go index b9d1f4fed..3df6b6d24 100755 --- a/pkg/apis/ceph.rook.io/v1/types.go +++ b/pkg/apis/ceph.rook.io/v1/types.go @@ -1727,8 +1727,12 @@ type KeystoneSpec struct {...
/remove wontfix
/remove wontfix
I have a gut feeling that this is not so easy. Especially with function pointers. I also assume that there should be mutexes.
designate dalmatian should be fixed with this commit: https://github.com/gophercloud/gophercloud/pull/3390/commits/fd91aa8f061449414ab966f8fc2b435d02e6d909 UPD: it should, but doesn't :(
when application credentials are created with access rules, these rules must be honored by the end service, e.g. neutron, nova or cinder. and these services must be configured accordingly, e.g....
@eshulman2 could you please provide more debug details on with and wo the `OpenStack-Identity-Access-Rules` header?
do we have an upstream octavia bug report?
I’ve realized that this PR unintentionally introduces a security issue. The `OpenStack-Identity-Access-Rules: 1.0` header signals that a client or gophercloud-based service supports access rules. When this header isn't set, keystone...
> I am not familiar with any openstack services relying on gophercloud that are not clients (like TF or ORC) @eshulman2 there is a lot of proprietary and opensource (e.g....