brainy-ocean-92780
01/14/2021, 7:30 PMbrainy-ocean-92780
01/14/2021, 7:31 PMwitty-market-32785
01/15/2021, 7:23 PMbrave-winter-60074
01/18/2021, 11:38 AMbrave-winter-60074
01/18/2021, 2:55 PMprehistoric-nail-50687
01/18/2021, 7:42 PMoperationalinsights.getWorkspace()
to get the id of a `Log Analytics workspace`:
const insightsWorkspaceId = operationalinsights
.getWorkspace({
resourceGroupName: `tal-env-ci`,
workspaceName: `tal-logs`,
})
.then((w) => w.id);
and use it to create a new DiagnosticSetting
new monitoring.DiagnosticSetting(
`diagnostic-setting`,
{
name: `diagnostic-setting`,
targetResourceId: app.id,
logAnalyticsWorkspaceId: insightsWorkspaceId,
logs: [ ...
This works fine, but for some reason, Pulumi wants to update the DiagnosticSetting
with every single run (even if nothing changes in the whole stack). The reason seems to be, that getWorkspace()
returns the the workspace ID with some characters in upper case, but when it gets saved, it changes to lowercase (see Microsoft.OperationalInsights
):
~ logAnalyticsWorkspaceId: "/subscriptions/fd90a697-afda-4fdd-9b9e-2bdffe0d2601/resourceGroups/tal-env-ci/providers/Microsoft.OperationalInsights/workspaces/tal-logs" => "/subscriptions/fd90a697-afda-4fdd-9b9e-2bdffe0d2601/resourcegroups/tal-env-ci/providers/microsoft.operationalinsights/workspaces/tal-logs"
Is this a known problem, is there any way around it?magnificent-television-29869
01/19/2021, 1:28 PMtall-needle-56640
01/19/2021, 5:42 PMPulumi.Azure.Storage.Blob
? I can't find it in Pulumi or the Azure rest spec.brave-winter-60074
01/20/2021, 2:45 PMrapid-oil-61997
01/21/2021, 5:10 PM$ pulumi up
error: malformed resource value: id must be a string
brainy-ocean-92780
01/22/2021, 6:30 PMglamorous-helmet-50600
01/22/2021, 9:46 PMfancy-jelly-61092
01/25/2021, 10:20 AMglamorous-helmet-50600
01/25/2021, 11:02 AMbrave-winter-60074
01/25/2021, 12:50 PMglamorous-helmet-50600
01/25/2021, 5:07 PMglamorous-helmet-50600
01/25/2021, 11:12 PMred-lighter-44012
01/27/2021, 5:04 PMdns name
.
TL DR: How do I look up an existing k8s Service (LoadBalancer) created via a helm chart (ingress controller)?faint-dog-16036
01/27/2021, 8:15 PMerror: open keeper <azurekeyvault://foo.vault.azure.net/keys/pulumi>: failed to Dial default KeyVault: Invoking Azure CLI failed with the following error:
There's no output after the :
, even if I throw in like --logtostderr -v=10
. This is with AZURE_KEYVAULT_AUTH_VIA_CLI
set to true
. If I don't have it set to true, the program just hangs when I try to switch.brave-winter-60074
01/28/2021, 10:30 AM<https://api-management-zg057f.azure-api.net/api/v1/customers/v1>
<https://api-management-zg057f.azure-api.net/api/v1/incidents/v1/{shortId}/comments>
brainy-ocean-92780
01/28/2021, 10:24 PMbitter-bear-28592
02/01/2021, 5:56 AMglamorous-helmet-50600
02/01/2021, 12:58 PMPulumi up
? I'd like to be able to debug/step through but I'm not sure if/how this is possible.glamorous-helmet-50600
02/01/2021, 3:08 PMglamorous-helmet-50600
02/01/2021, 9:54 PMfancy-umbrella-67692
02/01/2021, 11:12 PMpulumi new
selected azure typescript, all the defaults, then pulumi preview
and I get the above error. Related to this github issue I logged a while back: https://github.com/pulumi/pulumi-azure/issues/707brainy-ocean-92780
02/02/2021, 10:45 PMbrainy-ocean-92780
02/03/2021, 4:12 PMboundless-airport-99052
02/03/2021, 5:04 PMtall-needle-56640
02/04/2021, 9:07 PMvar resourceGroupVar = Output.Create(GetResourceGroup.InvokeAsync(new GetResourceGroupArgs
{
ResourceGroupName = resourceGroupNameParam,
}));
However, if the developer wants resource group creation to be part of their Pulumi stack, the obvious code would be
var resourceGroupVar = new ResourceGroup(...);
The problem is that these return different types, Output<GetResourceGroupResult>
and ResourceGroup
, so if I wanted to switch from one to the other, all the other generated code results in errors because Output.Apply()
isn't needed (or allowed) anymore. Looking closer, I determine that I can do this to avoid the errors.
var resourceGroupVar = Output.Create(new ResourceGroup(...));
But I'd only want to code it this way to avoid rewriting the converted code. I'd much prefer to treat all my resources the same (i.e. The return object is not of type Output<T>
. To be more consistent, would it be possible to create GetResourceGroup.Invoke()
that returned type GetResourceGroupResult
.tall-needle-56640
02/04/2021, 9:07 PMvar resourceGroupVar = Output.Create(GetResourceGroup.InvokeAsync(new GetResourceGroupArgs
{
ResourceGroupName = resourceGroupNameParam,
}));
However, if the developer wants resource group creation to be part of their Pulumi stack, the obvious code would be
var resourceGroupVar = new ResourceGroup(...);
The problem is that these return different types, Output<GetResourceGroupResult>
and ResourceGroup
, so if I wanted to switch from one to the other, all the other generated code results in errors because Output.Apply()
isn't needed (or allowed) anymore. Looking closer, I determine that I can do this to avoid the errors.
var resourceGroupVar = Output.Create(new ResourceGroup(...));
But I'd only want to code it this way to avoid rewriting the converted code. I'd much prefer to treat all my resources the same (i.e. The return object is not of type Output<T>
. To be more consistent, would it be possible to create GetResourceGroup.Invoke()
that returned type GetResourceGroupResult
.sparse-park-68967
02/05/2021, 8:39 PMinvokeAsync
when location is not specified for resources in the arm templates and it tries to determine by querying the resource group. We are about to add support for inferring the default location from the resource group (i.e. fix https://github.com/pulumi/pulumi-azure-nextgen/issues/6 - should be in the next release) directly in the provider. In which case arm2pulumi would no longer generate the invokeAsync
anymore and hopefully all other references can stick to the resource-group name instead. Are there other situations outside of location inference that the invokeAsync
is being called for you?tall-needle-56640
02/07/2021, 8:32 PMresourcegroup().location
), but I'd be happy to require one in the config if it meant I could avoid InvokeAsync
.sparse-park-68967
02/08/2021, 6:17 PMresourcegroup().location
use case - this will emit the invokeAsync
. If you omit it in the arm template, invokeAsync will be avoided since the provider will take care of that resolution itself in the next release