Open drusellers opened 4 months ago
Could you provide more context, like an error message or some more detail on what you expected vs what happened?
❯ pulumi up
Previewing update (dev)
View in Browser (Ctrl+O): https://app.pulumi.com/drusellers/groundwork/dev/previews/494be034-eb37-4586-9062-cfd21c2fac1c
Type Name Plan Info
pulumi:pulumi:Stack groundwork-dev
└─ dnsimple:index:ZoneRecord test-record 1 error
Diagnostics:
dnsimple:index:ZoneRecord (test-record):
error: must provide api token: must define a token for the dnsimple provider or set the DNSIMPLE_TOKEN environment variable
but it works with
❯ DNSIMPLE_ACCOUNT=... DNSIMPLE_TOKEN=... pulumi up
Previewing update (dev)
View in Browser (Ctrl+O): https://app.pulumi.com/drusellers/groundwork/dev/previews/22ce627e-29b5-48b2-95e1-f1dbcd23860a
Type Name Plan
pulumi:pulumi:Stack groundwork-dev
Resources:
2 unchanged
Do you want to perform this update? yes
Updating (dev)
View in Browser (Ctrl+O): https://app.pulumi.com/drusellers/groundwork/dev/updates/2
Type Name Status
pulumi:pulumi:Stack groundwork-dev
Resources:
2 unchanged
Duration: 1s
I think its odd that the static configuration isn't being respected. The classes are using Pulumi.Config
under the covers.
hi @drusellers - I just happened across this issue.
We're sorry you were having trouble here. We've since updated the landing page for dnsimple, which should show you an example of how to set up configuration via Pulumi.yaml
configuration file.
Read more about configuration here: https://www.pulumi.com/docs/iac/concepts/config/
What happened?
I was starting my Pulumi adventure and wanted to see if I could automate some DNS stuff in DNSimple. Because I'm just starting I didn't really want to muck around with ENV VAR so I thought I could use some kind of static configuration. I found
Pulumi.DNSimple.Config
and thought I could set those values. Alas, they weren't respected and had to revert to ENV VAR.Example
Output of
pulumi about
Additional context
I think that is everything.
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).