[FEATURE] Integration with Cirrus CI #5162
Replies: 4 comments
-
|
Hey @confused-Techie! This is cool! I haven't used Cirrus CI before but it'd be a great addition to Infisical's growing list of integrations 😄 I've added this to our roadmap. If you want, feel free to take a stab at it! The integrations code for Infisical is very flexible and easy to work with, so I'm sure it's do-able. Also check out our community Slack if you haven't yet — it's best for communicating/coordinating. |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic! Thanks for adding it. And I'll have to find some time to check it out when I can, but good to know where I can turn in case I have any questions |
Beta Was this translation helpful? Give feedback.
-
|
@dangtony98 @vmatsiiako Hi! Is this issue still available? I’d like to take it up and implement the Cirrus CI integration. assign me? |
Beta Was this translation helpful? Give feedback.
-
|
We’re reorganising our GitHub issues list. All feature requests will now be moved to the [feature request discussions (https://github.com/Infisical/infisical/discussions/categories/feature-request)] and users can upvote them to prioritise. This way, we can select features as our list empties. Moving this to discussion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Feature description
Being able to integrate closer with Cirrus CI as a build platform and retrieve secrets from it would be amazing, and super helpful for those utilizing that platform.
Why would it be useful?
For those on the platform, being able to import secrets, especially authentication tokens or signing keys would be very helpful to keep the configuration all in one place.
Additional context
While I don't yet know the full scope of this issue I'd be more than happy to help out wherever possible! (Especially if on the JavaScript side of things!)
Beta Was this translation helpful? Give feedback.
All reactions