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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kubernetes YAML ConfigGroupArgs and ConfigFileArgs to Accept Inputty Types #2203

Closed
Tracked by #2785
, #2784
...
phillipedwards opened this issue Oct 14, 2022 · 4 comments
Closed
Tracked by #2785
, #2784
...

Kubernetes YAML ConfigGroupArgs and ConfigFileArgs to Accept Inputty Types #2203

phillipedwards opened this issue Oct 14, 2022 · 4 comments
Assignees
@EronWright
Labels
kind/enhancement Improvements or new features mro1 Monica's list of 1st tier overlay related issues resolution/fixed This issue was fixed

Comments

@phillipedwards
Copy link
Member

Hello!

  • Vote on this issue by adding a 馃憤 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Currently, ConfigGroupArgs and ConfigFileArgs accept prompt values only which does not work when you have a non-prompt value(s) aka pulumi.Input | pulumi.Output.

Affected area/feature
@phillipedwards phillipedwards added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Oct 14, 2022
@phillipedwards
Copy link
Member Author

https://www.pulumi.com/registry/packages/kubernetes/api-docs/yaml/configgroup/#properties

@guineveresaenger guineveresaenger removed the needs-triage Needs attention from the triage team label Oct 17, 2022
@lblackstone
Copy link
Member

For historical context, the prompt value requirement was to improve previews since you couldn鈥檛 tell what would be provisioned otherwise. If you need to use Inputty types with the YAML, Helm, or Kustomize SDKs, I鈥檇 suggest wrapping those resources in an apply.

This will likely be addressed in the future by rewriting these resources as Multi-language Components, or similar. The following issues are related:
#1971
#2181

@lblackstone lblackstone removed their assignment Oct 17, 2022
@phillipedwards
Copy link
Member Author

Thank's for the context @lblackstone.

@mnlumi mnlumi added the mro1 Monica's list of 1st tier overlay related issues label Mar 28, 2023
This was referenced Mar 29, 2024
Open
Closed
Closed
Closed
@EronWright EronWright added the resolution/fixed This issue was fixed label Apr 17, 2024
@EronWright EronWright self-assigned this Apr 17, 2024
@EronWright
Copy link
Contributor

This feature is available now with the new "v2" implementations, enjoy!
https://www.pulumi.com/blog/kubernetes-yaml-v2/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EronWright EronWright

Labels
kind/enhancement Improvements or new features mro1 Monica's list of 1st tier overlay related issues resolution/fixed This issue was fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@EronWright @lblackstone @guineveresaenger @phillipedwards @mnlumi