Skip to content

Step for infisical to inject secrets into the bitrise pipeline

License

Notifications You must be signed in to change notification settings

CodeFishStudio/infisical-bitrise-step

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Infisical-secrets

Use this step to access your cloud or self hosted infisical secrets and inject them into your pipeline.

How to use this Step

Can be run directly with the bitrise CLI, just git clone this repository, cd into it's folder in your Terminal/Command Line and call bitrise run test.

Check the bitrise.yml file for required inputs which have to be added to your .bitrise.secrets.yml file!

Step by step:

  1. Open up your Terminal / Command Line
  2. git clone the repository
  3. cd into the directory of the step (the one you just git cloned)
  4. Create a .bitrise.secrets.yml file in the same directory of bitrise.yml (the .bitrise.secrets.yml is a git ignored file, you can store your secrets in it)
  5. Check the bitrise.yml file for any secret you should set in .bitrise.secrets.yml
  • Best practice is to mark these options with something like # define these in your .bitrise.secrets.yml, in the app:envs section.
  1. Once you have all the required secret parameters in your .bitrise.secrets.yml you can just run this step with the bitrise CLI: bitrise run test

An example .bitrise.secrets.yml file:

envs:
- infisical_client: "The client ID from infisical"
- infisical_client_secret: "Infisical Client Secret"
- infisical_project_id: "Infisical Project ID"
- infisical_env: "The slug of the environment you whish to access for your given project"
- infisical_url: "The url of the infisical environment you wish to access, defaults to cloud environment"
- infisical_path: "Path to the secrets within your project"

That's all ;)

About

Step for infisical to inject secrets into the bitrise pipeline

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages