Skip to content
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

Turn on more tests, record remaining failures #679

Merged
merged 1 commit into from
Nov 15, 2024
Merged

Conversation

Frassle
Copy link
Member

@Frassle Frassle commented Nov 15, 2024

This turns on the remaining already passing conformance tests for YAML, and records a reason why the remaining failing tests are failing.

@Frassle Frassle added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label Nov 15, 2024
@Frassle Frassle marked this pull request as ready for review November 15, 2024 06:55
@Frassle Frassle requested a review from a team as a code owner November 15, 2024 06:55
"l2-invoke-options": "cannot assign expression",
"l2-map-keys": "missing expected dependency primitive",
"l2-provider-grpc-config-schema-secret": "Detected a secret leak in state",
"l2-invoke-secrets": "YAML does not support fn::secret",
Copy link
Contributor

Choose a reason for hiding this comment

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

What does this mean? YAML has a fn::secret here:

case "fn::secret":
. Is this different from what we need? Can we describe that a bit more to avoid confusing others as well?

Copy link
Member Author

Choose a reason for hiding this comment

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

That's just the error message I got when running this test, I didn't dig into it deeper.

@Frassle Frassle merged commit 3e70006 into main Nov 15, 2024
6 checks passed
@Frassle Frassle deleted the fraser/l2-tests branch November 15, 2024 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants