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

[sdk/python] Handle CRDs with status field input #2183

Merged
merged 2 commits into from
Sep 21, 2022

Conversation

lblackstone
Copy link
Member

@lblackstone lblackstone commented Sep 20, 2022

Proposed changes

Although .status is an output-only field for CRDs, this is a frequent occurrence in real-world manifests. Manually delete the status field in the YAML handler to avoid an error on deserialization.

Related issues (optional)

Fix #800
Fix #1481

Although .status is an output-only field for CRDs, this is a frequent occurrence in real-world manifests. Manually delete the status field in the YAML handler to avoid an error on deserialization.
@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@lblackstone lblackstone merged commit bb1c93d into master Sep 21, 2022
@pulumi-bot pulumi-bot deleted the lblackstone/py-crd-status branch September 21, 2022 23:43
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.

Support CRD creation with .status field pulumi_kubernetes.yaml.ConfigFile with CRD raises TypeError
2 participants