Passing secrets to the session

[Matthias Gaiser _K15t_]

Hey everyone,

I'm currently trying out the Rovo Dev in Jira features.

My plan is to let Rovo Dev work on developing a simple Forge app. I've created the Forge app myself to have a basic setup running. Now, I wonder what's the best way to let Rovo Dev also handle the forge deployment and installation for me.

I'd like to pass my forge credentials as the environment variables FORGE_EMAIL and FORGE_API_TOKEN to the session so it automatically picks up the authentication. However, the secrets are only available to the setup script - so how do you share secrets with your session?

I'm then instructing RovoDev to parse that file as environment variables.

Is there an easier way for that?

[Ibrahim Khalil]

To securely share secrets with your Rovo Dev session for Forge deployments, you should define them as environment variables within your repository's CI/CD settings (like GitHub Actions or GitLab CI) or directly in your Jira automation rules. Since Rovo Dev picks up context from your environment, you can use a setup script to export these secrets into the session's active shell, ensuring they aren't hardcoded or exposed in logs.