feat: compute_snapshot_schedule_attach/list

[gryczj]

Description

Fixes #

Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.

Checklist

• I have followed guidelines from CONTRIBUTING.MD and Samples Style Guide
• Tests pass: npm test (see Testing)
• Lint pass: npm run lint (see Style)
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• This pull request is from a branch created directly off of GoogleCloudPlatform/nodejs-docs-samples. Not a fork.
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new sample directory, and I created GitHub Actions workflow for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

[snippet-bot]

Here is the summary of changes.

You are about to add 2 region tags.

• compute/snapshotSchedule/attachSnapshotSchedule.js:20, tag compute_snapshot_schedule_attach
• compute/snapshotSchedule/snapshotScheduleList.js:20, tag compute_snapshot_schedule_list

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[code-review-assist-experimental]

Hi @gryczj and reviewers,

I'm currently reviewing this pull request and will post my detailed review in a few minutes. In the meantime, here's a quick summary to help everyone get up to speed:

This pull request adds functionality for managing Compute Engine snapshot schedules. Specifically, it introduces three new JavaScript samples:

• createSnapshotSchedule.js: Creates a new snapshot schedule with customizable settings (daily, weekly, or monthly; retention policy; labels).
• attachSnapshotSchedule.js: Attaches an existing snapshot schedule to a Compute Engine disk.
• deleteSnapshotSchedule.js: Deletes a snapshot schedule. Note that this will fail if the schedule is attached to a disk.

Each sample includes comprehensive comments and error handling. Unit tests are also provided in attachSnapshotSchedule.test.js to verify the functionality.

The intent is to provide developers with clear, concise examples for working with Compute Engine snapshot schedules using the Node.js client library. This enhances the documentation and makes it easier for users to automate disk snapshots.

---

And now, a little haiku to lighten the mood:

Code flows like a stream,
Tests run, bugs swim downstream,
Clean code shines so bright.

Looking forward to the discussion!

[gryczj]

sample was added for testing purposes

[gryczj]

sample was added for testing purposes

[kweinmeister]

Can you please try to fix the conflict @gryczj ?

[rsamborski]

@BigBlackWolf PTAL

[BigBlackWolf]

Oh, I noticed that wrote a comment, but didn't submit 😅 Thanks, @rsamborski

Can you please try to fix the conflict @gryczj ?

Joanna is on vacations and I am going to support her with open PRs. @kweinmeister I've resolved the conflicts, do you have any other concerns?

[code-review-assist]

Gemini encountered an error creating the walkthrough. You can try again by commenting @code-review-assist walkthrough.

[iennae]

@code-review-assist walkthrough

[umairidris]

@code-review-assist walkthrough

[code-review-assist]

Gemini encountered an error creating the walkthrough. You can try again by commenting @code-review-assist walkthrough.

[umairidris]

@code-review-assist walkthrough

[code-review-assist]

Gemini encountered an error creating the walkthrough. You can try again by commenting @code-review-assist walkthrough.

[umairidris]

@code-review-assist walkthrough

[code-review-assist]

Gemini encountered an error creating the walkthrough. You can try again by commenting @code-review-assist walkthrough.

[m-strzelczyk]

The users that are currently failing CLA had CLA signed at the time they were committing the changes. Please force-merge the PR.