big-potato-91793
05/02/2023, 7:57 PMwooden-queen-36575
05/03/2023, 12:27 AMPulumi.<env>.yaml
files. But, if I do something like, pulumi stack init dev
, say without one of these Pulumi.xxx.yaml
files in place, it would generate a file called Pulumi.dev.yaml
, and a stack called dev
. Then, if I attempt this in another project folder, it can't create the stack because there is already a stack named dev
. There is no --config-file
parameter on the stack init
command, so I can't do something like, pulumi stack init <project>-<env> --config-file Pulumi.dev.yaml
flat-pager-43269
05/03/2023, 9:23 AMazure:network:NetworkInterface (network-interface):
error: deleting urn:pulumi:dev-4063::sepio-prime-vm::azure:network/networkInterface:NetworkInterface::network-interface: 1 error occurred:
* deleting Network Interface: (Name "network-interface86d62a7a" / Resource Group "rg-dev-406355a65e90"): network.InterfacesClient#Delete: Failure sending request: StatusCode=40
0 -- Original Error: Code="NicInUse" Message="Network Interface /subscriptions/06791571-1deb-46b0-96db-ffaa450f2e71/resourceGroups/rg-dev-406355a65e90/providers/Microsoft.Network/netwo
rkInterfaces/network-interface86d62a7a is used by existing resource /subscriptions/06791571-1deb-46b0-96db-ffaa450f2e71/resourceGroups/RG-DEV-406355A65E90/providers/Microsoft.Compute/virtualMachines/vm2f86b574. In order to delete the network interface, it must be dissociated from the resource. To learn more, see <http://aka.ms/deletenic|aka.ms/deletenic>." Details=[]
stocky-father-68249
05/03/2023, 10:35 AMaws.lb.listener
in the default_actions
attribute? I can't do it while creating the actual listener, because the listener is part of another stack. Any help or pointers would be appreciated.abundant-umbrella-49346
05/03/2023, 12:09 PMbusy-napkin-83700
05/03/2023, 2:45 PMCurrent runner version: '2.304.0'
Operating System
Runner Image
Runner Image Provisioner
GITHUB_TOKEN Permissions
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Error: Unable to resolve action `actions/setup-node@v3.5`, unable to find version `v3.5`
delightful-salesclerk-16161
high-grass-3103
05/03/2023, 4:24 PMsparse-intern-71089
05/03/2023, 5:58 PMwet-fall-57893
05/03/2023, 11:50 PM@pulumi/kubernetes
npm package?abundant-umbrella-49346
05/04/2023, 1:19 AMadorable-manchester-22573
05/04/2023, 7:48 AMquick-king-51158
05/04/2023, 10:34 AMresource "kubernetes_manifest" "foo_mci" {
provider = ...
depends_on = ...
manifest = { ... }
wait {
fields = {
# check ingress has an IP
"<http://status.VIP|status.VIP>" = "^(\\d+(\\.|$)){4}"
}
}
timeouts {
create = "5m"
update = "5m"
delete = "1m"
}
}
polite-sandwich-68547
05/04/2023, 1:19 PM[resource plugin cloudflare-3.6.0] installing
[resource plugin aws-4.38.1] installing
[resource plugin aws-5.38.0] installing
rich-motorcycle-3089
05/04/2023, 3:37 PMlemon-monkey-228
05/04/2023, 6:04 PM--target
flag to limit the scope of the changes depending upon the trigger (ie. triggered by another repository) . This would be especially easy if you used a ComponentResource
to encapsulate each applicationās resource boundarys. Plus you could still get re-use of these individual `ComponentResource`s by packaging them (npm) and importing them.
I also think itād be pretty cool if Pulumi had a first class notion of tags/labels that you could then limit the scope of changes to (eg. --target-tag="<http://my.org/application=foo|my.org/application=foo>"
)
(Sorry for the brain dump)careful-family-14644
05/04/2023, 9:34 PM<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>K9YP96TZTKGKZNQM</RequestId>
<HostId>3bCPcjHFP7NlNej0xq17DsabAq9E9ghuFcmwhTC/zSikw7Xk67/GaLBY4dII/3Zu1Rxs5eswMIY=</HostId>
</Error>
polite-sandwich-68547
05/05/2023, 8:02 AMpolite-sandwich-68547
05/05/2023, 8:03 AMmillions-furniture-75402
05/05/2023, 11:32 AMbusy-electrician-64079
05/05/2023, 2:37 PMnice-application-79035
05/05/2023, 5:52 PMmany-television-17079
05/05/2023, 7:05 PMred-scooter-62880
05/06/2023, 1:24 PMwooden-queen-36575
05/07/2023, 6:03 PMpulumi up
, I can see that annotations I wish to place on the service are included in the plan, but when I actually run it, the resulting service only has a single <http://kubectl.kubernetes.io/last-applied-configuration|kubectl.kubernetes.io/last-applied-configuration>
that includes my annotation amongst others, but all other annotations are gone, see in thread...freezing-belgium-97648
05/08/2023, 8:25 AMchilly-tailor-89151
05/08/2023, 10:44 AMfull-parrot-46337
05/08/2023, 2:51 PMfreezing-belgium-97648
05/08/2023, 3:48 PMdry-pilot-49577
05/08/2023, 4:58 PMarn:aws:lambda:us-west-2:345057560386:layer:AWS-Parameters-and-Secrets-Lambda-Extension-Arm64:4
what happens - error: operation error CloudControl: UpdateResource, https response error StatusCode: 400, RequestID: zzzzz, api error ValidationException: Model validation failed (#: required key [Code] not found)
The total diff in pulumi is just the addition of the lambda layer. However, the error seems to imply that cloudcontrol needs code
as part of the update-function call. Hoping for a pointer or a workaround. Debug information in thread.
pulumi version: 3.66.0 (typescript code)
search tags: lambda layer Code cloudcontrol