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

Unable to version an explicit provider from config #508

Open
t0yv0 opened this issue Oct 5, 2023 · 1 comment · May be fixed by #510
Open

Unable to version an explicit provider from config #508

t0yv0 opened this issue Oct 5, 2023 · 1 comment · May be fixed by #510
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec

Comments

@t0yv0
Copy link
Member

t0yv0 commented Oct 5, 2023

What happened?

Trying to set the version of an explicit provider from outside the stack, running into unexpected error messages from Pulumi YAML. Is there a way to do this?

Example

name: test

runtime:
  name: yaml

config:
  version:
    type: string

resources:

  provider:
    type: pulumi:providers:aws
    options:
      version: ${version}

  tested-resource:
    type: aws:s3/bucket:Bucket
    properties:
      bucket: testbucket-${pulumi.stack}
    options:
      provider: ${provider}
pulumi config set version 5.42.0
pulumi preview
error: failed to discover plugin requirements: Pulumi.yaml:15,16-26: version must be a string; 

Output of pulumi about

CLI          
Version      3.86.0
Go Version   go1.21.1
Go Compiler  gc

Host     
OS       darwin
Version  14.0
Arch     x86_64

This project is written in yaml

Current Stack: t0yv0/test/buckett

Found no resources associated with buckett

Found no pending operations associated with buckett

Backend        
Name           pulumi.com
URL            https://app.pulumi.com/t0yv0
User           t0yv0
Organizations  t0yv0, pulumi
Token type     personal

No dependencies found

Pulumi locates its logs in /var/folders/gk/cchgxh512m72f_dmkcc3d09h0000gp/T/ by default

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@t0yv0 t0yv0 added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Oct 5, 2023
@Zaid-Ajaj
Copy link
Contributor

The solution to this issue looks very similar to #507, I'll assign it to myself ✅

@Zaid-Ajaj Zaid-Ajaj removed the needs-triage Needs attention from the triage team label Oct 6, 2023
@Zaid-Ajaj Zaid-Ajaj self-assigned this Oct 6, 2023
@Zaid-Ajaj Zaid-Ajaj added this to the 0.95 milestone Oct 6, 2023
@Zaid-Ajaj Zaid-Ajaj linked a pull request Oct 10, 2023 that will close this issue
@justinvp justinvp modified the milestones: 0.95, 0.96 Oct 24, 2023
@mikhailshilkov mikhailshilkov modified the milestones: 0.96, 0.97 Nov 23, 2023
@justinvp justinvp modified the milestones: 0.97, 0.98 Dec 18, 2023
@justinvp justinvp modified the milestones: 0.98, 0.99 Jan 8, 2024
@justinvp justinvp modified the milestones: 0.99, 0.100 Jan 29, 2024
@justinvp justinvp removed this from the 0.100 milestone Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants