{
  "id": 3106194,
  "title": "Day 31: Stash Keeps What Status Won't Show, and Private Is a Flag, Not a Subnet",
  "url": "https://urgent.news/2026/08/24/day-31-stash-keeps-what-status-wont-show-and-private-is-a-flag-not-a",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-24T20:12:31.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ndcodes/day-31-stash-keeps-what-status-wont-show-and-private-is-a-flag-not-a-subnet-1hkc"
  },
  "original_language": "en",
  "account": "Two specific lessons were learned during this experience. First, Git's stash feature creates a hidden work area that is not displayed by git status. To restore a specific stash entry, use git stash apply with the stash index number, and use git stash apply --index to also restore the staged state. Second, creating a private MySQL RDS instance on AWS requires configuring the instance with several specific settings. This includes providing a private subnet group, specifying storage autoscaling parameters, and setting the --no-publicly-accessible flag to prevent the instance from receiving a public DNS name. Additionally, the CLI requires creating a subnet group manually, which includes specifying subnets in at least two availability zones.",
  "summary": "Both of today's tasks involved something real that the interface never mentions. Git keeps work in a place that git status will not tell you about. The RDS console wizard builds a resource on your behalf and never says it did. Neither is a bug, and both cost you time the first time you meet them. One Git task, one AWS task. Park uncommitted work with stash and bring a specific entry back, then…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}