(Posted by @roger on behalf of a customer on Slack)
Currently, for our Content Management API (CMA), the environment parameter defines whether the client works against the main/primary env or a sandbox. It’s currently optional, and the client will default to the primary env if not otherwise specified. While convenient, this can also be risky for those not expecting it, such as plugin authors who use it to make changes to other records.
While we can’t change it for existing versions without breaking backward compatibility, would it be worth considering making this a required parameter for future versions, so that API users would have to explicitly specify which env they want to operate on?
Original message:
It is a bit scary that the management API defaults to main (which is production for most people). Maybe that should be a required param for the build client so more newcomers like us don’t make the same mistake. We were very lucky to have a different field name when we were lucky to not edit our whole prod setup when we tried it out in a test env
