Why graduation requirements for every new deploy?

Question

For a fast moving agile development team, the requirement to pass graduation requirements for all permissions when any new permission is added is a huge bottleneck in productivity.

Why is it necessary to repeat this process for ALL permissions???

This is a very poor developer experience. We now have to document and basically make a full test suite of fake, non-production-like conditions to trigger all the requirements again.

Every time we consider building out a new feature using your API, this is a completely unnecessary bottleneck. We really like the RC api other than this, but we seriously consider changing platforms each time as this seems like such an "anti-developer" practice.

Page 1 / 1

This is actually followed in order to make sure you application doesn't break in actual production in real-time. Therefore this process is strictly followed everytime with all the criteria and requirements.. While I know it's actually a very frustrating process everytime, but the best you can do is do contact the backend dev team and ask them to speed up the process

Reply

Anirban2396911020 · Answer

This is actually followed in order to make sure you application doesn't break in actual production in real-time. Therefore this process is strictly followed everytime with all the criteria and requirements.. While I know it's actually a very frustrating process everytime, but the best you can do is do contact the backend dev team and ask them to speed up the process

Reply

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded