Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sfn update does not populate parameters from --apply-stack outputs #310

Open
yongjun-chee opened this issue Oct 18, 2023 · 0 comments · May be fixed by #311
Open

sfn update does not populate parameters from --apply-stack outputs #310

yongjun-chee opened this issue Oct 18, 2023 · 0 comments · May be fixed by #311

Comments

@yongjun-chee
Copy link

Hi,
When I create a new stack with --apply-stack option, it populates parameters from the given stack's output successfully without prompting.

...
[Sfn]: Outputs for stack: sfn-stack-1
[Sfn]:    Ssm Stop Role Arn1: arn:aws:iam::123412341234:role/SSM_Stop_RDS_rds-test
...
$ sfn create --defaults --yes sfn-stack-2 --apply-stack sfn-stack-1 --file ./template2.json
[Sfn]: SparkleFormation: create
[Sfn]:   -> Name: sfn-stack-2
[Sfn]: Stack runtime parameters:
[Sfn]: Events for Stack: sfn-stack-2
Time                        Resource Logical Id   Resource Status      Resource Status Reason   
2023-10-18 13:08:11 -0400   sfn-stack-2           CREATE_IN_PROGRESS   User Initiated           
2023-10-18 13:08:14 -0400   KeepRDSStopped1                                         CREATE_IN_PROGRESS                                 
2023-10-18 13:08:14 -0400   WaitHandle                                              CREATE_IN_PROGRESS                                 
2023-10-18 13:08:15 -0400   WaitHandle                                              CREATE_IN_PROGRESS   Resource creation Initiated   
2023-10-18 13:08:15 -0400   WaitHandle                                              CREATE_COMPLETE                                    
2023-10-18 13:08:16 -0400   KeepRDSStopped1                                         CREATE_IN_PROGRESS   Resource creation Initiated   
2023-10-18 13:08:16 -0400   KeepRDSStopped1                                         CREATE_COMPLETE                                    
2023-10-18 13:08:17 -0400   AutomationAWSStopRdsInstance1SsmMaintenanceWindowTask   CREATE_IN_PROGRESS                                 
2023-10-18 13:08:18 -0400   AutomationAWSStopRdsInstance1SsmMaintenanceWindowTask   CREATE_IN_PROGRESS   Resource creation Initiated   
2023-10-18 13:08:18 -0400   AutomationAWSStopRdsInstance1SsmMaintenanceWindowTask   CREATE_COMPLETE                                    
2023-10-18 13:08:19 -0400   sfn-stack-2                                             CREATE_COMPLETE                                    
[Sfn]: Stack create complete: SUCCESS
[Sfn]: Stack description of sfn-stack-2:
[Sfn]: Outputs for stack: sfn-stack-2
[Sfn]:    Ssm Stop Role Arn1: arn:aws:iam::123412341234:role/SSM_Stop_RDS_rds-test

However, if I run sfn update using sfn update --defaults --yes sfn-stack-2 --apply-stack sfn-stack-1 --file ./template2.json command to include a new output as a new parameter, it doesn't populate the value, instead it's prompting user input.

...
[Sfn]: Outputs for stack: sfn-stack-1
[Sfn]:    Ssm Stop Role Arn2: arn:aws:iam::123412341234:role/SSM_Stop_RDS_rds-test2
[Sfn]:    Ssm Stop Role Arn1: arn:aws:iam::123412341234:role/SSM_Stop_RDS_rds-test
...
$ sfn update --defaults --yes sfn-stack-2 --apply-stack sfn-stack-1 --file ./template2.json
[Sfn]: SparkleFormation: update
[Sfn]:   -> Name: sfn-stack-2 Path: ./template2.json
[Sfn]: Stack runtime parameters:
[Sfn]: Ssm Stop Role Arn2:

I'm using sfn (v3.1.8) from ruby - v2.6.10 and here is the gem list. Could you take a look into this, please? @chrisroberts

addressable (2.8.5, 2.8.1)
attribute_struct (0.4.4)
bigdecimal (default: 1.4.1)
bogo (0.2.16)
bogo-cli (0.3.2, 0.3.1, 0.2.18)
bogo-config (0.3.1)
bogo-ui (0.1.28)
bundler (2.4.20, default: 2.2.3)
cmath (default: 1.0.0)
colored (1.2)
command_line_reporter (4.0.3)
cs-asna-sf-pack (0.1.0)
csv (default: 3.0.9)
date (default: 2.0.3)
dbm (default: 1.0.0)
did_you_mean (1.3.0)
domain_name (0.5.20190701)
e2mmap (default: 0.1.0)
etc (default: 1.0.1)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.1.0)
forwardable (default: 1.2.0)
gdbm (default: 2.0.0)
graph (2.8.2)
hashdiff (0.2.3)
hashie (5.0.0)
http (3.3.0)
http-cookie (1.0.5)
http-form_data (2.3.0)
http_parser.rb (0.6.0)
io-console (default: 0.4.7)
ipaddr (default: 1.2.2)
irb (default: 1.0.0)
jmespath (1.6.2)
json (default: 2.1.0)
logger (default: 1.3.0)
matrix (default: 0.1.0)
miasma (0.3.8)
miasma-aws (0.3.30)
miasma-azure (0.1.4)
miasma-google (0.1.0)
miasma-open-stack (0.1.4)
miasma-rackspace (0.1.2)
miasma-terraform (0.1.2)
mime-types (3.5.1)
mime-types-data (3.2023.1003)
minitest (5.11.3)
multi_json (1.15.0)
multi_xml (0.6.0)
mutex_m (default: 0.1.0)
net-ssh (7.2.0)
net-telnet (0.2.0)
openssl (default: 2.1.2)
ostruct (default: 0.1.0)
paint (2.3.0)
power_assert (1.1.3)
prime (default: 0.1.0)
psych (default: 3.1.0)
public_suffix (5.0.3)
rake (12.3.3)
rdoc (default: 6.1.2.1)
rexml (3.2.6, default: 3.1.9.1)
rss (default: 0.2.7)
rubygems-update (3.2.3)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
sfn (3.1.8)
shell (default: 0.7)
slop (3.6.0)
sparkle_formation (3.0.40)
stringio (default: 0.0.2)
strscan (default: 1.0.0)
sync (default: 0.5.0)
test-unit (3.2.9)
thwait (default: 0.1.0)
tracer (default: 0.1.0)
unf (0.1.4)
unf_ext (0.0.8.2)
webrick (default: 1.4.4)
xml-simple (1.1.9)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant