Prepend migrated legacy examples to resource samples#17680
Merged
Conversation
melinath
approved these changes
May 21, 2026
Collaborator
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit c639468: Diff reportYour PR generated the following diffs in downstream repositories:
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode 🟢 All tests passed in Replaying mode! No Recording was needed. View the replaying VCR build log |
MikolajLuczko
pushed a commit
to MikolajLuczko/magic-modules
that referenced
this pull request
May 28, 2026
gitika-yadav
pushed a commit
to gitika-yadav/magic-modules
that referenced
this pull request
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ensures that legacy examples converted to samples (in-memory) are prepended and ordered before any newly added samples.
Since the generator uses the first example to generate any iam/datasource/list resource - this is to ensure any new samples added won't change what config is used to generate those tests before the migration is fully completed.
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.