In order to resolve this, an sts command will need to be run to assume the correct role in the code here:
let aliases: pulumi.Alias[] = [];
if (!args.disableManagedObjectAliases) {
aliases = [{
name: "sync-command",
}];
}
//TODO assume a role here or something
new command.local.Command(`${name}-sync-command`, {
create: syncCommand,
update: syncCommand,
delete: deleteCommand,
environment: {
LAST_MODIFIED: new Date(folderContents.summary.lastModified).toString(),
},
}, { parent: this, aliases });
I was planning on a PR for this, but I couldn't find a way to get the role from the provider / using the aws.getXXX functions, so not sure how to resolve this.
Output of pulumi about
Package version is: 0.11.1
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).
What happened?
Whilst setting
ManagedObjects = false
the command that is run does not respect the providerExample
The following code will not work
Because the command that gets run when ManagedObjects are set to false:
does not respect the role that is assumed.
In order to resolve this, an sts command will need to be run to assume the correct role in the code here:
I was planning on a PR for this, but I couldn't find a way to get the role from the provider / using the
aws.getXXX
functions, so not sure how to resolve this.Output of
pulumi about
Package version is:
0.11.1
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).