Support Multiple Activation Keys or Permit Activation Keys per Environment

Currently Stackify provides a single activation key per account. In the happy path for Stackify instrumentation this isn't a problem. In other scenarios, this is less than ideal.

• If the key is compromised in some way and needs to be reissued

• If the key is committed to version control, it should still ideally be rolled even if there is no known compromise of the repository

• If an employee with previous access to the key leaves or is terminated, there might be a desire to roll the API key

• For separation of environments it would be great to ensure keys are not shared across environments

In any scenario that leads to generating a new key, there is not graceful to handle the switch. We cannot stage changes ahead of generation because we don't have the key, and once we do have the key, any integrations that rely on it will immediately stop logging until we can update app configs or cycle through deployments.

Other tooling in the space at least allows you to generate a key per environment which would allow us to better roll out changes, but ideally we should be able to generate multiple API keys so that they can remain active for a period of time allowing us to perform the necessary deployments and changes without outage.