Secret
A secret is sensitive information, such as a credential, token, or cryptographic key, whose unauthorized disclosure could compromise security.
Practical Automation with PowerShell: Effective scripting from the console to the cloud
A secret is confidential sensitive data, such as a credential, password, connection value, or API key, that requires protected storage and controlled access.
- How it is used
- Protects automation credentials and connection values by moving them out of scripts into vault-backed retrieval.
- How deep it goes
- Explains vault selection, naming, storage types, retrieval behavior, and connection tests; defers vault setup and registration.
- Examples
- Demonstrates SQL health-check credentials, a SQL Server instance name, and SendGrid email values stored and tested from separate vaults.
- What you can do after
- Apply it via SecretManagement cmdlets to store, retrieve, name, and test secrets across multiple vaults.
Shipping Go: Develop, deliver, discuss, design, and go again
A secret is sensitive configuration data, such as a credential, stored so authorized automation can access it without exposing its value.
- How it is used
- Uses sensitive credentials for deployment automation and application configuration without placing them in ordinary files.
- How deep it goes
- Explains repository storage, Kubernetes references, and security limits, but defers implementation of a robust external secret manager.
- Examples
- Uses a GCP JSON credential in GitHub and a Redis password referenced by a Kubernetes deployment.
- What you can do after
- Operate/configure GitHub and Kubernetes deployments by storing credentials and injecting passwords through secret references.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains secret →
.NET in Action, Second Edition
A secret is sensitive information, such as a credential or cryptographic key, that must be protected from unauthorized disclosure.
- How it is used
- Protects sensitive values while supplying applications with the connection data they need.
- How deep it goes
- Distinguishes secrets from ordinary configuration and demonstrates local storage and configuration-based retrieval.
- Examples
- Uses a database connection string, .NET Secret Manager commands, Kubernetes secrets, and Azure App Service environment variables.
- What you can do after
- Apply it via .NET Secret Manager to store a local connection string and read it through application configuration.
Related concepts
- external access integrationused by · An external access integration is a Snowflake object that governs outbound access from Snowflake code to external network locations using specified network rules and secrets.
- SecretManagementused by · SecretManagement is a PowerShell module framework that provides a common interface for storing and retrieving secrets through registered vault extensions.
- managed identityaddressed by · A managed identity is a nonhuman digital identity whose credentials and lifecycle are administered by a cloud or infrastructure service, allowing workloads to authenticate to supported resources without managing credentials directly.
- configurationcontrasts with · A specification of settings, parameters, or component relationships that determines how a system, application, model, or process is structured or operates.
- Azure Key Vaultused by · Azure Key Vault is a Microsoft Azure managed service for securely storing and controlling access to secrets, cryptographic keys, and certificates.
- credentialuses · A credential is information or an artifact presented as evidence of an entity’s identity, qualifications, status, or authorization to access a system or resource.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.