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

Fix: cloud-platform-account plan pipeline failing #6492

Open
9 tasks
jaskaransarkaria opened this issue Nov 21, 2024 · 0 comments
Open
9 tasks

Fix: cloud-platform-account plan pipeline failing #6492

jaskaransarkaria opened this issue Nov 21, 2024 · 0 comments

Comments

@jaskaransarkaria
Copy link
Contributor

Background

https://concourse.cloud-platform.service.justice.gov.uk/teams/main/pipelines/infrastructure-account/jobs/terraform-plan/builds/215

╷

│ Error: Failed to decode resource from state

│ 

│ Error decoding "module.sso.auth0_client.saml" from previous state: missing expected [

╵

│   with aws_s3_bucket_object.kubeconfig,

│   on main.tf line 233, in resource "aws_s3_bucket_object" "kubeconfig":

│  233: resource "aws_s3_bucket_object" "kubeconfig" {

│ 

│ use the aws_s3_object resource instead

│ 

│ (and one more similar warning elsewhere)

╷

│ Error: missing expected [

│ 

│   with auth0_client.opensearch_app_logs,

│   on app-opensearch.tf line 399, in resource "auth0_client" "opensearch_app_logs":

│  399:   addons {

│ 

╵

╷

│ Error: missing expected [

│ 

│   with auth0_client.opensearch,

│   on modsec-opensearch.tf line 218, in resource "auth0_client" "opensearch":

│  218:   addons {

│ 

╵

╷

│ Error: missing expected [

│ 

│   with module.sso.auth0_client.saml,

│   on .terraform/modules/sso/auth0.tf line 12, in resource "auth0_client" "saml":

│   12:   addons {

│ 

╵

╵



Proposed user journey

Approach

Which part of the user docs does this impact

Communicate changes

  • post for #cloud-platform-update
  • Weeknotes item
  • Show the Thing/P&A All Hands/User CoP
  • Announcements channel

Questions / Assumptions

Definition of done

  • readme has been updated
  • user docs have been updated
  • another team member has reviewed
  • smoke tests are green
  • prepare demo for the team

Reference

How to write good user stories

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant