Project Level API keys when deploying bundles

NN

Hi Dataiku Team,
I am trying to create a project level API key which can be used to execute scenarios in that single project from an external application.
I created the API ID and secret in the project security in the Design Instance ( or Dev)
This secret works and the external application is able to run the scenario on DSS Design

I bundled the project and promoted to AUtomation Instance (Prod)
Now the challenge is that the API key i defined in Design (Dev) is getting carried over to Automation (PROD)

If i try to delete the promoted API key on Automation and create a new API Key for PROD , the next time i promote a new bundle the automation API Key gets deleted and the one from Design (Dev) gets copied over once more.

Wanted to know if anyone has seen a similar issue or has an suggestions on what the best way to have separate keys for Design and AUtomation Instances

Any doc reference or suggestions are welcome. Thanks.

Operating system used: Linux

Turribeach

https://community.dataiku.com/discussion/comment/44048#Comment_44048

You can use a pre-hook to store the Automation key in the Designer project, then use a post hook to remove the Designer one from the Automation node and remove the Automation key from the Designer node.

Turribeach

Project Level API keys will always included in bundles. If you want to keep separation you should use level API keys and have specific service/generic users which have access to specific folders/projects/groups. If that's not your liking you could remove all projects keys from the Automation node as part of a post Deployer hook.

NN

Thanks @Turribeach
Post Deployer hook looks promising to remove Design Key, but it may not help me retain the API Key we define in the Automation Instance.

Anyway for now it looks like i will retain the same key in both instance till i explore the post hook.