ancient-solstice-53934
09/12/2022, 7:35 AMripe-park-70944
09/13/2022, 11:58 AMazure:*
auth settings for the same service principal that azure-native:*
uses, but I'm getting the following error:
error: failed to load application credentials:
Details: 1 error occurred:
* A Subscription ID must be configured when authenticating as a Service Principal using a Client Secret.
azure:subscriptionId
is definitely configured, could this error be masking something else? Is there an issue with running Azure Native and Azure Classic side by side?curved-eye-56312
09/14/2022, 8:50 AMpulumi up
the errors are thrown and provisioning fails
Is there any way I can implement the logic I have mentioned without having those errors blocking my deployment?few-lizard-48557
09/15/2022, 8:26 AMdamp-honey-93158
09/15/2022, 12:37 PMStorage = new StorageAccount($"{InputArgs.DevOpsProjectShortName}store", new StorageAccountArgs()
{
EnableHttpsTrafficOnly = true,
EnableNfsV3 = false,
Kind = "StorageV2",
ResourceGroupName = Runtime.InfraResGroupName,
Location = InputArgs.Location,
Sku = new Pulumi.AzureNative.Storage.Inputs.SkuArgs()
{
Name = "Standard_LRS"
},
AllowBlobPublicAccess = false
});
StorageFileShare = new FileShare($"{InputArgs.DevOpsProjectName}share", new()
{
AccountName = Storage.Name,
ResourceGroupName = Runtime.InfraResGroupName,
ShareName = "migration"
});
I am a little confused... I don't know why the pulumi system thinks that the file share is worth replacing... this is the partial output from a subsequent pulumi up (with refresh and diff):
[provider=urnšulumi:creditor-test:šrojects:šulumi:providers:azure-native::default_1_73_0::bb23b3b0-c386-4ed9-8f78-0f5c59555be7]
- accessTier: "TransactionOptimized"
- shareQuota: 5120
--outputs:--
- accessTier : "TransactionOptimized"
- accessTierChangeTime: "2022-09-15T12:33:40.0000000Z"
- etag : "\"0x8DA971685991300\""
- lastModifiedTime : "2022-09-15T12:33:41.0000000Z"
- shareQuota : 5120
--outputs:--
Help appreciated and thank you!bored-activity-40468
09/15/2022, 6:34 PMbig-australia-4159
09/16/2022, 12:12 PMazure-native
on pulumi and am trying to import an existing blobcontainer to my pulumi stack. My issue is that I can't figure out how to get the ID
for the blobcontainer.
I have gotten the storage account imported but am not able to find the ID for the container as provided in the example here. Does anyone know what azure cli command I can run to get the ID? I have tried storage container show
but that does not return an ID in the format as shown in the example import statement.millions-journalist-34868
09/16/2022, 1:33 PMgorgeous-accountant-60580
09/21/2022, 9:23 AMbulky-kite-69343
09/21/2022, 2:42 PMancient-solstice-53934
09/26/2022, 7:42 PMvar containerApp= new ContainerApp(appName, new ContainerAppArgs
{
Configuration = new ConfigurationArgs
{
Dapr = new DaprArgs
{
AppPort = 80,
AppProtocol = "http",
Enabled = true,
},
Ingress = new IngressArgs
{
External = false,
TargetPort = 80
},
Secrets = new InputList<SecretArgs>
{
new SecretArgs { Name = "registry-password", Value = "testpassword"}
},
Registries = new InputList<RegistryCredentialsArgs> // From other subscription
{
new RegistryCredentialsArgs
{
Server ="<http://testacr.azurecr.io|testacr.azurecr.io>",
Username = "testacr",
PasswordSecretRef = "registry-password"
}
}
}
}
but get ERROR: The resource with name 'testacr' and type 'Microsoft.ContainerRegistry/registries' could not be found in subscription 'sub2'.
In workaround I have tried following CLI command to add registry from other subscription to container app and it works
az containerapp registry set -n MyContainerapp -g MyResourceGroup
--server MyExistingContainerappRegistry.azurecr.io --username MyRegistryUsername --password MyRegistryPassword
Do we have any similar workaround in Pulumi?bored-airplane-19518
09/27/2022, 1:53 PMbitter-twilight-16606
09/28/2022, 8:19 AMripe-russia-4239
09/28/2022, 11:51 AMPulumi.AzureNative.Subscription.Alias
)? I'm trying to achieve this in line with the "Landing Zones" architecture, but Pulumi just hangs during the preview
operation šimportant-london-46196
09/30/2022, 7:28 AMnice-guitar-97142
09/30/2022, 4:19 PMerror: Preview failed: autorest/azure: Service returned an error. Status=400 Code="MissingApiVersionParameter" Message="The api-version query parameter (?api-version=) is required for all requests."
narrow-cat-84237
10/01/2022, 6:18 PMsparse-area-37315
10/07/2022, 7:08 PMmammoth-agency-10350
10/10/2022, 5:20 PM2022/10/10 10:12:39 azureblob: constructed service URL: <azure storage account url>
2022/10/10 10:12:39 azureblob.URLOpener: using shared key credentials
sparse-fountain-4597
10/11/2022, 10:40 AMgorgeous-accountant-60580
10/12/2022, 9:59 AMmammoth-agency-10350
10/13/2022, 5:43 PMadventurous-butcher-54166
10/14/2022, 12:58 PMpulumi-azure-native
Python SDK (seems to apply to all languages though) and there seems to be a missing property. The property is public_network_access
which sets network access configurations for a storage account (see screenshot from Azure Portal). This property was introduced in the Azure API spec for storage accounts in 2021-06-01
but the provider seems to be generating the SDK based on a very old spec 2021-02-01
with 5 newer versions available, the newest being 2022-05-01
and Azure using 2021-09-01
in their docs.
Azure REST API docs, showing version 2021-09-01, with the property available:
https://learn.microsoft.com/en-us/rest/api/storagerp/storage-accounts/create?tabs=HTTP
Pulumiās storage.StorageAccount where the property was first available:
https://github.com/pulumi/pulumi-azure-native/blob/master/sdk/python/pulumi_azure_native/storage/v20210601/storage_account.py#L43
Current storage.StorageAccount:
https://github.com/pulumi/pulumi-azure-native/blob/master/sdk/python/pulumi_azure_native/storage/storage_account.py
Questions
⢠How come the SDK is based on such an old spec for storage accounts?
⢠Is it considered okay to use other versions of the spec in code? Like referencing: storage.v20220501.storage_account
wet-noon-14291
10/15/2022, 10:41 PMripe-russia-4239
10/17/2022, 8:48 AMcreamy-byte-37608
10/18/2022, 2:17 PMlate-lizard-19909
10/18/2022, 3:26 PM"Code="InvalidRequestBody" Message="The value of the parameter 'properties.subnetId' is invalid."
However specifying a subnet ID is only available at the Premium SKU and gives this error if specified: Message="Feature properties.subnetId requires a Premium sku to be set.
I'm not really sure how to get this to work at the basic tier. I've tired setting PublicNetworkAccess: "Enabled"
, but still get the same issuelate-lizard-19909
10/18/2022, 3:31 PMmicroscopic-furniture-52860
10/19/2022, 2:39 PMaz storage file upload
but would like an update to be triggered if the file contents changes. I could possibly hack around this by changing the filename each time, but thatās not ideal and easily forgotten.
Unfortunately this doesnāt look like itās supported in the spec even though it was in az classic: https://pulumi-community.slack.com/archives/C84L4E3N1/p1648163487694929?thread_ts=1648066957.732819&cid=C84L4E3N1
I briefly looked into a Dynamic Provider but thatās not supported in dotnet. Any suggestions welcome šwhite-helicopter-55877
10/19/2022, 4:50 PMwhite-helicopter-55877
10/19/2022, 4:50 PMcontroller.service.loadBalancerIP
directive. Using
const regEngineIngress = new k8s.helm.v3.Chart(
"sample-engine-ingress",
{
repo: "<http://kubernetes.github.io|kubernetes.github.io>",
chart: "ingress-nginx",
version: "4.3.0",
fetchOpts: {
repo: "<https://kubernetes.github.io/ingress-nginx>",
},
namespace: clusterSvcsNamespace.metadata.name,
values: {
controller: {
replicaCount: 2,
nodeSelector: {
"kubernetes\.io/os": "linux",
},
service: {
loadBalancerIP: publicIp.ipAddress,
}
}
},
},
{ provider: k8sProvider },
);
That way, the public IP is assigned and since the public IP gets a A record automatically, it works nicely.