Skip to content

fix: preserve parent module context in references #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

ajkerrigan
Copy link
Member

@ajkerrigan ajkerrigan commented Jun 18, 2025

Include the parent module path when identifying references, otherwise we'll skip those references when building references metadata blocks.

Drive-by: Make enough changes to the CI configuration so that c7n-left tests run, following the upstream switch to uv

Include the parent module path when identifying references, otherwise we
won't be able to match them later.
@ajkerrigan ajkerrigan force-pushed the ajk/fix/module-reference-paths branch from 013fc62 to af324f2 Compare June 18, 2025 06:41
adapt changes from upstream
so we can seed it with c7n-left dependencies, layer an editable tfparse
over top of it, and run tests.
Use a custom function to produce a fully-qualified reference path
instead of performing a string replace on the output of
`reference.HumanReadable()`. This is probably a more stable way to track
references inside modules.
@ajkerrigan ajkerrigan force-pushed the ajk/fix/module-reference-paths branch from 7749390 to 5088f56 Compare June 23, 2025 19:55
@ajkerrigan ajkerrigan merged commit d8c629e into cloud-custodian:main Jun 23, 2025
12 checks passed
@ajkerrigan ajkerrigan deleted the ajk/fix/module-reference-paths branch June 23, 2025 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants