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

[TS] Pass provider to yaml resources #1996

Closed
wants to merge 1 commit into from
Closed

Conversation

blampe
Copy link
Contributor

@blampe blampe commented May 27, 2022

Proposed changes

This plumbs a provider through a few yaml flows that were implicitly relying on the default provider.

This only covers TS for now -- from the linked issues it seems this might still affect some of the other languages.

I'm not sure how to best test this -- locally it resolved an issue I was seeing with yaml.ConfigGroup, but I haven't verified kustomize, helm/v2, etc. I was thinking of setting disable-default-providers on a couple of the CI examples, but that feels pretty blunt...

Related issues (optional)

Refs #1938 #1945

@github-actions
Copy link

PR is now waiting for a maintainer to run the acceptance tests. This PR will only perform build and linting.

Note for the maintainer: To run the acceptance tests, please comment /run-acceptance-tests on the PR

@lblackstone
Copy link
Member

@blampe Thanks for the PR! I think we should go ahead and fix this across all of our SDKs, so @viveklak and I are planning to work on that later this week. I like the idea of using disable-default-providers in at least one test to make sure that we've covered our bases here.

@lblackstone
Copy link
Member

I've opened #2005 with fixes for all SDKs and relevant test cases. Thanks again for getting the ball rolling here!

@lblackstone lblackstone closed this Jun 7, 2022
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.

2 participants