Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
機械支援の翻訳下書き (Japanese) for "Environment Approval Step": Environment Approval Step is a devops workflow control that requires review before a sensitive change proceeds for configuration for a runtime stage. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Environment Approval Step when staging and production drifted, so the team could keep high-risk automation accountable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Infrastructure Approval Step": Infrastructure Approval Step is a devops workflow control that requires review before a sensitive change proceeds for cloud resources and platform wiring. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Infrastructure Approval Step when a new region was added, so the team could keep high-risk automation accountable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Secret Build Gate": Secret Build Gate is a devops quality gate that blocks promotion when required checks fail for credential and sensitive configuration. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Build Gate when a token rotated, so the team could prevent broken releases before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Scheduler Workload Priority": Scheduler Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for placement of work onto resources. It uses priority classes, preemption rules, and fairness limits so teams can protect critical paths while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Scheduler Workload Priority when the cluster needed to place a job, so the team could protect critical paths before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Virtual Machine Runtime Profile": Virtual Machine Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for isolated guest compute. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Virtual Machine Runtime Profile when the VM migrated hosts, so the team could target optimization work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "TLS Anycast Endpoint": TLS Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for encrypted transport setup. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used TLS Anycast Endpoint when a certificate neared expiration, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Incident Artifact Signature": Incident Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for response to service degradation. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Incident Artifact Signature when on-call received a high-severity page, so the team could trust deployed packages before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Queue Placement Strategy": Queue Placement Strategy is a compute scheduling rule that chooses where workloads should run for asynchronous work buffer. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Queue Placement Strategy when the queue depth increased, so the team could improve reliability and efficiency before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Release Secret Rotation": Release Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for versioned delivery of code or content. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Release Secret Rotation when the release notes were generated, so the team could reduce credential exposure before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "DNS Traffic Shaper": DNS Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for name resolution and delegation. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used DNS Traffic Shaper when a resolver returned stale data, so the team could protect important traffic before traffic crossed a service boundary.”