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

Don't check QName is valid in alias logic #9950

Merged
merged 2 commits into from Jun 23, 2022
Merged

Don't check QName is valid in alias logic #9950

merged 2 commits into from Jun 23, 2022

Conversation

Frassle
Copy link
Member

@Frassle Frassle commented Jun 23, 2022

Description

We really need to sort out what are actually valid names and validate them correctly, but that's part of #8949. For now assume it's fine to throw any string in here because it's been working so far.

Fixes #9947

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

Copy link
Member

@iwahbe iwahbe left a comment

Choose a reason for hiding this comment

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

This keeps biting us. Should we consider this a 4.0 change?

@Frassle
Copy link
Member Author

Frassle commented Jun 23, 2022

Should we consider this a 4.0 change?

Yes probably.

@Frassle Frassle merged commit a7c8d62 into master Jun 23, 2022
@pulumi-bot pulumi-bot deleted the fraser/qname branch June 23, 2022 21:53
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.

resource name requirements have changed
2 participants