DeploymentSettings
doesn't handle the agent pool id if it's a secret and fails/ignore silently
#419
Labels
Milestone
What happened?
I have stack
a
that creates anAgentPool()
✔. That stack exports theagent_pool
as an object that containsid
,name
andtoken
(secret) ✔.Another stack output
agent-pool-id-secret
exports the pool id as a secret ✔.The stack output is like this.
I have a stack
b
that retrieves that retrieves the 2 stack outputs as stack references from stacka
. ✔Stack
b
creates aDeploymentSettings()
and uses theagent-pool.id
(which should be a string) as part of the resource creation.The
DeploymentSettings()
is created BUT theagent_pool_id
is never set ❌.After additional investigation, I wondered if passing the
secret
instead of anoutput
could be the issue (step 5 onward) and it appears this seems to be the case. If theagent_pool_id
receives a secret, then the value somehow isn't used ❌Steps to reproduce
b
Pulumi hosted pool
) ❌b
agent_pool_id_secret
instead ofagent_pool['id']
for theagent_pool_id
propertyb
Pulumi hosted pool
) ❌pulumi up --refresh
correctly showsdiff: +agentPoolId
✔b
Pulumi hosted pool
) ❌Workaround
For now, it's possible to workaround this temporarily by remove the secrets and using plain text values. However, this is problematic because using an object as a stack reference accounts for 1 resource only where using multiple stack references will account for more resources and ultimately increase the cost passed on the customer.
Example
Stack
a
Stack
b
Output of
pulumi about
Additional context
In part related to pulumi/pulumi#17422
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).
The text was updated successfully, but these errors were encountered: