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

chore: fixing issue with biztalk360 #2162

Closed
wants to merge 2 commits into from
Closed

chore: fixing issue with biztalk360 #2162

wants to merge 2 commits into from

Conversation

jcountsNR
Copy link
Contributor

Summary

SImple fix for biztalk ID

@jcountsNR jcountsNR requested a review from seemantk as a code owner December 8, 2023 19:09
Copy link

github-actions bot commented Dec 8, 2023

Thank you for your contribution, our team will be reviewing this shortly, please be available for any follow up questions or code review feedback!

@jcountsNR
Copy link
Contributor Author

I think there is a problem with the check here. It's saying that the display name is already taken, which not really true. I'm just trying to change the id because I have to reference it in the marketplace.

ERROR: The following errors occurred while validating: biztalks360

  • dataSourceMetadata/displayName: displayName has already been taken

Copy link

Old PRs will be closed after 30 days of inactivity. This PR has been quiet for 14 days and is being marked as stale. Reply here to keep this PR open.

@jcountsNR
Copy link
Contributor Author

@rahulbasu-nr , I'm not sure if you know the answer to this one. Someone put the id for the datasource here as third-party-biztalk360, and I'm trying to fix it into something more usable for the marketplace. Is it possible to change the ID of a data-source once it's been set? And if so, how can I resolve the schema compliance error?

@aswanson-nr aswanson-nr removed the stale label Jan 3, 2024
@jcountsNR jcountsNR closed this Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants