Skip to content

Conversation

@ptgott
Copy link
Contributor

@ptgott ptgott commented Jan 8, 2026

Check whether the resource reference was generated correctly. Currently, we never execute the step called Check if resource reference docs are up to date if a PR updates the resource reference generator configuration.

Also edit the resource reference generator config so re-running the generator would not produce diffs.

@ptgott ptgott force-pushed the paul.gottschling/2026-01-08-resource-ref-filter branch from 2c3c04b to 45b8e38 Compare January 8, 2026 15:51
@ptgott
Copy link
Contributor Author

ptgott commented Jan 8, 2026

Example of a failure related to the appropriately configured path filter: https://github.com/gravitational/teleport/actions/runs/20822630955/job/59815168824?pr=62707#step:11:9

- 'docs/pages/reference/infrastructure-as-code/terraform-provider/**'
- 'docs/pages/reference/infrastructure-as-code/teleport-resources/**'
- 'examples/chart/teleport-cluster/charts/teleport-operator/operator-crds'
- 'build.assets/tooling/cmd/resource-ref-generator/config.yaml'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is changing the config file the only thing we should be concerned with here? What if I changed any of the resource-ref-generator code?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point—fixed in this push.

Check whether the resource reference was generated correctly. Currently,
we never execute the step called `Check if resource reference docs are
up to date` if a PR updates the resource reference generator
configuration or code.

Also edit the resource reference generator config so re-running the
generator would not produce diffs.
@ptgott ptgott force-pushed the paul.gottschling/2026-01-08-resource-ref-filter branch from 45b8e38 to 811a418 Compare January 9, 2026 13:22
@ptgott ptgott added the no-changelog Indicates that a PR does not require a changelog entry label Jan 9, 2026
@ptgott ptgott requested a review from rosstimothy January 9, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/branch/v18 no-changelog Indicates that a PR does not require a changelog entry size/sm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants