Railway Integration + Service Accounts #491
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… service accounts/tokens
This was referenced Apr 15, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description 📣
This PR adds a ton of new features (some enabled/disabled):
Railway Integration: The Infisical-Railway integration is finally here, and we support syncing to both Railway shared variables at the project-level as well as service variables at the service-level. This makes Infisical a total powerhouse for managing any secrets configuration for projects and services on Railway.
Service Accounts (currently disabled usage on endpoints): Service Accounts are an effort to create a type of authentication client that strikes a greater balance between the existing Service Token (scoped to a project and environment with crypto capabilities) and API keys (can mimic a user but without crypto capabilities). Since Service Accounts come with an Access Key and Private Key, they have the ability to authenticate with the API whilst also performing cryptographic operations, making them handy to represent any machine client.
The vision for service accounts is to standardize authentication with the Infisical API but also to power more complex secrets workflows such as having a more powerful client capable of generating (short-lived) service tokens.
Type ✨
Bug fix
New feature
Breaking change
Documentation
I have read the contributing guide, agreed and acknowledged the code of conduct. 📝