curved-dress-32683
09/20/2020, 7:40 PMhandsome-zebra-11018
09/21/2020, 2:26 AMenv
variables to container. Is there any way I can define env variables as an array in yaml file and loop through then in my typescript file instead of coding each variable.
This is what I have today in yaml
config:
pro:key1:value1
pro:key2:value2
and this is how I am using them in my typescript file
env: [
{
name: "key1",
value: config.get("key1")
},
{
name: "key2",
value: config.get("key2")
},
This works fine but I have 30+ parameters and want the create env using loop instead of hardcoding every one in ts file
any help?
Something like
env: [
array.forEach((param :string) => {
const splitString = param.split(":");
{
name: splitString[0],
value: splitString[1]
}
})
],
helpful-farmer-76395
09/21/2020, 2:28 AMlittle-cartoon-10569
09/21/2020, 3:39 AMimport
opt. There have been a few changes on the way, most of which I've resolved using pulumi refresh
. Two that haven't yet been resolved are:
1. An IAM role created without a name or namePrefix, which has defaulted to using namePrefix = Pulumi name. In order to import it, I had to temporarily add the name property with its actual name. I now want to go back to using either the default or namePrefix. How do I get Pulumi to recognize that changing name: "myprefix-984ac6"
to namePrefix: "myprefix"
is no changed? I'm prepared to edit the state if needed.
2. My Directory was created with a password, which I'm now ignoring via ignoreChanges
(because I want to be able to change the password outside of Pulumi). If I leave ignoreChanges in, then Pulumi reports "resource 'dirname' has a problem: Missing required property 'password'".
Are either of these resolvable?famous-twilight-87777
09/21/2020, 7:11 AMfamous-twilight-87777
09/21/2020, 7:11 AMfamous-twilight-87777
09/21/2020, 7:11 AMlet assoc_bastion_ip = new os.networking.FloatingIpAssociate("associate_bastion_fip", {
floatingIp: bastion_ip.then(ip => ip.id),
portId: bastion.id
});
famous-twilight-87777
09/21/2020, 7:11 AMfamous-twilight-87777
09/21/2020, 7:12 AMDiagnostics:
openstack:networking:FloatingIpAssociate (associate_bastion_fip):
error: Unable to get ID of openstack_networking_floatingip_associate_v2 floating_ip 41142f29-54b9-44a7-bb33-8e6581634aa7: there are no openstack_networking_floatingip_v2 with 41142f29-54b9-44a7-bb33-8e6581634aa7 IP
famous-twilight-87777
09/21/2020, 7:13 AMfamous-twilight-87777
09/21/2020, 7:13 AMfloatingIp: bastion_ip.then(ip => ip.address)
famous-twilight-87777
09/21/2020, 7:14 AMfamous-twilight-87777
09/21/2020, 7:14 AMnutritious-shampoo-16116
09/21/2020, 10:27 AMfamous-twilight-87777
09/21/2020, 10:41 AMfamous-twilight-87777
09/21/2020, 10:41 AMconst assoc_bastion_ip = new os.networking.FloatingIpAssociate("associate_bastion_fip", {
floatingIp: bastion_ip,
portId: bastion.networks[0].port
});
famous-twilight-87777
09/21/2020, 10:42 AMfamous-twilight-87777
09/21/2020, 10:42 AMDiagnostics:
openstack:networking:FloatingIpAssociate (associate_bastion_fip):
error: openstack:networking/floatingIpAssociate:FloatingIpAssociate resource 'associate_bastion_fip' has a problem: Missing required property 'portId'
elegant-island-39916
09/21/2020, 11:00 AMpulumi_kubernetes
)
pulumi for k8s dashboard helm chart:
k8s_dash = helm.Chart(
"kubernetes-dashboard",
config=helm.ChartOpts(
repo="stable",
chart="kubernetes-dashboard",
version="1.5.2",
namespace="kube-system",
),
opts=pulumi.ResourceOptions(
providers={"kubernetes": cluster_provider}
),
)
output:
Diagnostics:
kubernetes:<http://rbac.authorization.k8s.io:Role|rbac.authorization.k8s.io:Role> (kube-system/kubernetes-dashboard):
warning: <http://rbac.authorization.k8s.io/v1beta1/Role|rbac.authorization.k8s.io/v1beta1/Role> is deprecated by <http://rbac.authorization.k8s.io/v1/Role|rbac.authorization.k8s.io/v1/Role> and not supported by Kubernetes v1.22+ clusters.
kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding> (kube-system/kubernetes-dashboard):
warning: <http://rbac.authorization.k8s.io/v1beta1/RoleBinding|rbac.authorization.k8s.io/v1beta1/RoleBinding> is deprecated by <http://rbac.authorization.k8s.io/v1/RoleBinding|rbac.authorization.k8s.io/v1/RoleBinding> and not supported by Kubernetes v1.22+ clusters.
kubernetes:extensions:Deployment (kube-system/kubernetes-dashboard):
error: apiVersion "extensions/v1beta1/Deployment" was removed in Kubernetes 1.16. Use "apps/v1/Deployment" instead.
See <https://git.k8s.io/kubernetes/CHANGELOG/CHANGELOG-1.16.md#deprecations-and-removals> for more information.
where can i adjust apiversion for pulumi to avoid this issue?adamant-byte-68515
09/21/2020, 12:18 PMred-area-47037
09/21/2020, 12:33 PMfuture-morning-96441
09/21/2020, 1:43 PMfatal error: heap out of memory
for several days now (using pulumi with node), Are there any known antipatterns in Pulumi, which can cause this?
It tried to use more verbose logging and tracing but couldn't find any hint about what is causing this. (see error message in my next message)
I vaguely guess this could be either during stack-output-serialization or serializing and packaging lambda-functions but I sadly don't have any hard evidence to pinpoint the location.
Does anyone have some advice on how to proceed analyzing this error or what can cause this?clever-byte-21551
09/21/2020, 6:02 PMPULUMI_CONFIG_PASSPHRASE_FILE
and I get this error:
FATA[0729] Failed to deploy error="failed to update infra stack: failed to update stack: failed to get stack outputs: code: 255\n, stdout: \n, stderr: error: decrypting secret value: failed to decrypt: incorrect passphrase, please set PULUMI_CONFIG_PASSPHRASE to the correct passphrase\n\n: failed to select stack: exit status 255"
Any idea why?
@broad-dog-22463clever-plumber-29709
09/21/2020, 10:01 PM$ pulumi stack import --file github.singular.checkpoint.json
error: could not deserialize deployment: constructing secrets manager of type "cloud": secrets (code=Unknown): NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
quiet-helicopter-40480
09/22/2020, 1:20 AMclever-plumber-29709
09/22/2020, 1:55 AMhandsome-zebra-11018
09/22/2020, 3:59 AMpulumi up
command is 10 mins? Can we reduce it via some config?
When I kill pulumi up and start new one.. it complains old one is still running..famous-twilight-87777
09/22/2020, 5:34 AMclever-byte-21551
09/22/2020, 5:36 AMfamous-twilight-87777
09/22/2020, 6:00 AM