I was told this issue is preventing us from using the API without creating a key that has __owner__ access. If that's true, then it... it seems outrageous?
I cannot open our system up to a ransomware attack because my team is trying to setup scripting for compliance and disaster recovery.
Is this truly under active development? It has been an open issue since 2020? Can additional resources be allocated and an estimate provided? Perhaps a smaller release could be cut to allow API keys with more granular permissions?
I obviously am not privy to your backlog, and I certainly understand the difficulty of prioritizing items like this instead of new features that would improve sales, but this seems pretty egregious if you would like your clients to pass compliance and have disaster recovery scripting.
Hopefully I am misunderstanding the situation and an alternative or workaround can be proposed. I would absolutely love to be wrong about this.
I was told this issue is preventing us from using the API without creating a key that has __owner__ access. If that's true, then it... it seems outrageous?
I cannot open our system up to a ransomware attack because my team is trying to setup scripting for compliance and disaster recovery.
Is this truly under active development? It has been an open issue since 2020? Can additional resources be allocated and an estimate provided? Perhaps a smaller release could be cut to allow API keys with more granular permissions?
I obviously am not privy to your backlog, and I certainly understand the difficulty of prioritizing items like this instead of new features that would improve sales, but this seems pretty egregious if you would like your clients to pass compliance and have disaster recovery scripting.
Hopefully I am misunderstanding the situation and an alternative or workaround can be proposed. I would absolutely love to be wrong about this.