brave-motorcycle-67487
09/12/2022, 11:02 PMpulumi new aws-python
. After looking at it, I realized I wanted to use the native python bindings for this, so I `rm -r`ed the directory and attempted to recreate it with pulumi new aws-native-python
. This isn't letting me do so though because the old project still exists in pulumi.com's state. I'm not sure how to delete it though because there doesn't seem to be any way to do that from the web ui, and I don't have any of the configuration files that told the cli about the project and stack. (There are no resources in it - I never ran pulumi up
- so it's just the project itself that I need to delete)delightful-salesclerk-16161
pulumi destroy
first to destroy all the resourcespulumi stack rm
to remove the stackbrave-motorcycle-67487
09/12/2022, 11:07 PM┌─[jamesph@Jamess-MBP] - [~/Documents/winfrastructure] - [Mon Sep 12, 04:06]
└─[$]> pulumi stack ls
error: could not detect current project: no Pulumi.yaml project file found (searching upwards from /Users/jamesph/Documents/winfrastructure). If you have not created a project yet, use `pulumi new` to do so: no project file found
┌─[jamesph@Jamess-MBP] - [~/Documents/winfrastructure] - [Mon Sep 12, 04:06]
└─[$]> pulumi stack rm staging
error: If you're using the --stack flag, pass the fully qualified name (org/project/stack): no Pulumi.yaml project file found (searching upwards from /Users/jamesph/Documents/winfrastructure). If you have not created a project yet, use `pulumi new` to do so: no project file found
pulumi stack rm xiongchiamiov/aws/staging
. And that cleaned up the project as well.little-cartoon-10569
09/12/2022, 11:15 PMbrave-motorcycle-67487
09/12/2022, 11:16 PMlittle-cartoon-10569
09/12/2022, 11:31 PMbrave-motorcycle-67487
09/12/2022, 11:34 PMstocky-restaurant-98004
09/13/2022, 1:50 PMbrave-motorcycle-67487
09/13/2022, 4:30 PMstocky-restaurant-98004
09/13/2022, 6:25 PMbrave-motorcycle-67487
09/13/2022, 6:52 PMTaskDefinitionContainerDefinition Args
but down on the page it says TaskDefinitionContainerDefinition
(without "Args"). The former appears to be the correct name. I've seen a few of those and so have been assuming Args just gets added somewhere or whatever.
2. The naming for ECS Task Definitions appears to be ignored and so I opened a bug for that yesterday: https://github.com/pulumi/pulumi-aws-native/issues/619
3. And then this thing about errors with immutable fields that I'm trying to figure out (which I don't know if that's a Native problem or a me problem): https://pulumi-community.slack.com/archives/CRH5ENVDX/p1663090433029689?thread_ts=1663090433.029689&cid=CRH5ENVDX
Is the issue tracker the best place to put things that I encounter and think might be bugs? Or is there a better place to discuss them and verify they're truly issues? Since this is brand new stuff I'm building, I'm happy to work off the cutting edge and help flush out issues, whatever's most helpfulstocky-restaurant-98004
09/17/2022, 2:33 PM