servicecatalog-puppet-deploy code build is failing after upgrding puppet module to 0.246.0 version with the error ::: File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/servicecatalog_puppet/commands/manifest.py", line 51, in assemble_manifest_from_ssm action_name = parts[4] IndexError: list index out of range

servicecatalog-puppet-deploy code build was failing when run for all the accounts with the below error: 2024-05-02T20:47:18.222Z INFO: Worker Worker(salt=695160401, workers=**, host=c56d35488f81, username=root, pid=464) was stopped. Shutting down Keep-Alive thread

2024-05-02T20:47:18.222Z INFO Thread-1 Worker Worker(salt=695160401, workers=**, host=c56d35488f81, username=root, pid=464) was stopped. Shutting down Keep-Alive thread

As referenced in issue #674(servicecatalog-puppet-bootstrap-spokes-in-ou Code buold job is failing with attribute Error #674)) We upgraded the version to the latest version . After upgrading ,when we trigger the code build for single account ,it is failing with the below error

Overridden parameters {'single_account': None, 'subset': {}} 203 | Expanding 204 | Traceback (most recent call last): 205 | File "/root/.pyenv/versions/3.9.17/bin/servicecatalog-puppet", line 8, in 206 | sys.exit(cli()) 207 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/click/core.py", line 764, in call 208 | return self.main(args, kwargs) 209 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/click/core.py", line 717, in main 210 | rv = self.invoke(ctx) 211 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/click/core.py", line 1137, in invoke 212 | return _process_result(sub_ctx.command.invoke(sub_ctx)) 213 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/click/core.py", line 956, in invoke 214 | return ctx.invoke(self.callback, ctx.params) 215 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/click/core.py", line 555, in invoke 216 | return callback(args, kwargs) 217 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/servicecatalog_puppet/cli.py", line 398, in expand 218 | manifest_commands.expand(f, puppet_account_id, regions, extra_params) 219 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/servicecatalog_puppet/commands/manifest.py", line 65, in expand 220 | assemble_manifest_from_ssm(target_directory) 221 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/servicecatalog_puppet/commands/manifest.py", line 51, in assemble_manifest_from_ssm 222 | action_name = parts[4] 223 | IndexError: list index out of range 224

Could you please help to resolve this as it impacts the deployments .

@eamonnfaherty ,could you please help on this issue?

sorry I missed this. I was not getting emails from github. Could you please share your manifest file.

Yes, this is the manifest file we had earlier

accounts:

default_region: eu-central-1
exclude: ous:
- /MaintenanceOU
- /Master
- /Security
- /Suspended name: "all-accounts" ou: / parameters: Path: default: /servicecatalog-puppet/ RoleName: default: PuppetRole regions_enabled:
  - eu-central-1
  - eu-west-2
  - us-east-1
  - eu-west-1 tags:
  - "scope:spoke" spoke-local-portfolios: global-optional-blueprints: associations:
  - "arn:aws:iam::${AWS::AccountId}:role/servicecatalog-puppet/PuppetRole"
  - "arn:aws:iam::${AWS::AccountId}:role/PlatformLZAdmin"
  - "arn:aws:iam::${AWS::AccountId}:role/AWSControlTowerExecution"
  - "arn:aws:iam::${AWS::AccountId}:role/ACNLZNetworkOperator" depends_on:
  - iam-blueprint
    deploy_to: tags:
- regions:
  - eu-central-1
  - eu-west-2
    tag: "scope:spoke" portfolio: aws-global-optional-blueprints

launches: iam-blueprint: deploy_to: tags:

regions: default_region tag: "scope:spoke" portfolio: aws-global-mandatory-blueprints product: iam-blueprint version: v1
test-blueprint: portfolio: aws-global-mandatory-blueprints product: test-blueprint
version: v1
parameters: EnvironUsed: default: prod CentralSSMAccount: ssm: name: /servicecatalog-puppet/manifest/AutomationAccount SNSEndpoint: ssm: name: /servicecatalog-puppet/manifest/SNSEndpoint
deploy_to: tags:
tag: scope:spoke regions:
- eu-central-1
- eu-west-2
- eu-west-1
As we got issue with the parameters defined in this manifest file, we had to remove the parameters defined using this path in the product test-blueprint. Hence, we have removed the parameters section from the product in the manifest to avoid getting issues related to these SSM parameters. Could you please assist here the format or the path to define the parameters in SSM Parameter store to parameterize using the manifest file.

Thanks , Ramya D

Hi @eamonnfaherty ,could you please help me with this issue on how we can define the SSM parameters in manifest file of service catalog puppet ?

Hi Eamonn,

I have updated the manifest file in github . Would you be able to check and assist me on this issue?

Thanks & Regards, Ramya Duraisamy Intelligent Cloud & Infrastructure,ATCI Bangalore Cell: +91 7899820781

From: Eamonn Faherty @.> Sent: Wednesday, July 3, 2024 7:46 PM To: awslabs/aws-service-catalog-puppet @.> Cc: Duraisamy, Ramya @.>; Author @.> Subject: [External] Re: [awslabs/aws-service-catalog-puppet] servicecatalog-puppet-deploy code build is failing after upgrding puppet module to 0.246.0 version with the error ::: File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/servicecatalog_pup...

CAUTION: External email. Be cautious with links and attachments.

sorry I missed this. I was not getting emails from github. Could you please share your manifest file.

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/awslabs/aws-service-catalog-puppet/issues/709*issuecomment-2206237519__;Iw!!OrxsNty6D4my!4uSWfyz1z5LuP9JIFoSp0yVjpADOo9MTqEWCv-mnBGct-qnefUsH-5FnOC-I2xNk0Gz7uEcUXr1xhAGvLGHZcPMrYzNI4Qw$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASWTW4DAU7DVZPZJMEZXOHDZKQBQTAVCNFSM6AAAAABKJVY2EGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBWGIZTONJRHE__;!!OrxsNty6D4my!4uSWfyz1z5LuP9JIFoSp0yVjpADOo9MTqEWCv-mnBGct-qnefUsH-5FnOC-I2xNk0Gz7uEcUXr1xhAGvLGHZcPMrqRckkzs$. You are receiving this because you authored the thread.Message ID: @.**@.>>

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.

awslabs / aws-service-catalog-puppet