Secrets

Many projects require the use of sensitive or secret variables such as API Keys that should not be committed to a GitHub repository. Aineko Cloud supports user-defined secrets that are injected in an Aineko pipeline at runtime.

Secrets are partitioned at an environment level, which means these values are created by the user for each environment, and are accessible only to pipelines in that environment.

Adding, deleting, or viewing secrets can be handled from the secrets page on the Aineko Cloud dashboard.

Secrets are updated only when a pipeline is updated

Secrets are injected into the pipeline runtime when it is started. After updating a secret, you will have to trigger a new deployment workflow (by making a GitHub commit), to see it in effect.

Updating a Secret

We do not store the values of secrets locally. Therefore, in order to update a secret value, you must first delete that secret and then add a new secret with the same name and environment, but with an updated value.