Add instance storage discovery patterns in config

[Ivaylogi98]

Note: Should merge forward these changes to ubuntu-noble.

Summary

Adds two config fields to the AWS agent settings baked into the stemcell, required by
cloudfoundry/bosh-agent#407 (and subsequently by cloudfoundry/bosh-agent#396) to correctly discover NVMe instance storage on AWS Nitro
instances.

Background

On Nitro-based instances (e.g. m6id, i3en), NVMe PCIe enumeration order is
non-deterministic — /dev/nvme0n1 may be the root EBS volume, an attached EBS volume,
or instance storage depending on boot order. The bosh-agent now uses symlinks in
/dev/disk/by-id/ to identify and exclude EBS volumes, leaving only instance storage.

To keep the resolver IaaS-agnostic, the AWS-specific patterns are not hardcoded in the
agent binary — they are injected via agent config at stemcell build time.

Changes

stemcell_builder/stages/bosh_aws_agent_settings/apply.sh:

• InstanceStorageDevicePattern: glob pattern matching all NVMe namespace devices
• InstanceStorageManagedVolumePattern: glob pattern matching EBS volume symlinks in
  /dev/disk/by-id/, used to identify and exclude EBS volumes from instance storage
  discovery

Related

• Fix nvme instance storage discovery bosh-agent#407 — implements the NVMe instance storage discovery using
  these patterns
• Implement Runtime NVMe Instance Storage Discovery Using AWS EBS Symlinks bosh-agent#396 — original PR this refactors
• Fix NVMe raw_instance_storage device enumeration for all instance families bosh-aws-cpi-release#196 — companion CPI-side change

This repository uses a "Merge Forward" strategy

Changes should be made in the earliest applicable branch, and
merged forward through subsequent branches.

1. Create a PR into the oldest branch (ubuntu-<short_name>)
2. After this PR has been merged create a merge-to-<next_short_name> branch
3. Merge ubuntu-<short_name> into merge-to-<next_short_name>
4. Create a PR to merge merge-to-<next_short_name> into ubuntu-<next_short_name>
5. Repeat as needed for subsequent branches

[coderabbitai]

Walkthrough

The apply.sh script in the bosh_aws_agent_settings stage has been updated to include additional configuration parameters in the generated agent.json file. Two new settings have been added to the Platform.Linux configuration: InstanceStorageDevicePattern (set to /dev/nvme*n1) and InstanceStorageManagedVolumePattern (set to /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_*). The existing UseMonitIptablesFirewall setting remains in place alongside these additions.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding instance storage discovery patterns to the AWS agent configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The PR description comprehensively covers the purpose, background, technical changes, and includes the required merge-forward strategy guidance from the template.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@stemcell_builder/stages/bosh_aws_agent_settings/apply.sh`:
- Around line 15-16: The two config keys InstanceStorageDevicePattern and
InstanceStorageManagedVolumePattern are dead fields (not consumed by
bosh-agent); either remove them from the agent config output in apply.sh or
implement support in bosh-agent to consume them. To fix: if removing, delete the
two keys from the config generation in apply.sh and update any docs/tests; if
implementing, add parsing and use of
InstanceStorageDevicePattern/InstanceStorageManagedVolumePattern inside the
DevicePathResolver logic (respecting existing DevicePathResolutionType,
DIDTransformPattern and VolumeID matching semantics), add unit tests to
bosh-agent that verify matching/resolution against /dev/disk/by-id/ symlinks,
and update integration tests to exercise managed vs instance-storage resolution
paths.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 53804f69-c57a-4da5-8162-a0753a10bc96

📥 Commits

Reviewing files that changed from the base of the PR and between 265a297 and f8f6b3a.

📒 Files selected for processing (1)

• stemcell_builder/stages/bosh_aws_agent_settings/apply.sh