refarchArchived
7 messages
Cloud Posse Reference Architecture
J
j4zzcatabout 1 year ago
'lo all
Does it make sense to create a deeper org hierarchy? and is it well supported by the terraform modules?
Does it make sense to create a deeper org hierarchy? and is it well supported by the terraform modules?
Christopher Mayoraabout 1 year ago
hey team, i forked this repo https://github.com/cloudposse-examples/app-on-eks-with-argocd but the actions on my org are not running anyone knows what can be happening no message or something that i can see on github
Marat Bakeevabout 1 year ago
If I want to deploy a ec2 instance based VPN solution for remote access, under the reference architecture - it goes to core-network account, or core-auto? Or core-corp?
Slackbotabout 1 year ago
This message was deleted.
E
erikabout 1 year ago
Where in the refarch docs do we say to replace these placeholders?
Christopher Mayoraabout 1 year ago
hey team, we are trying to deploy a website project which is using
and this is having like a conflict issue with the website repositorie
maybe we need to structure the website project in a different way?
yarn but during the deployment steps we saw that on the github-action-deploy-argocd is trying to runnpm install git-url-parse@14.0.0and this is having like a conflict issue with the website repositorie
Run npm install git-url-parse@14.0.0
297
npm error code ERESOLVE
298
npm error ERESOLVE unable to resolve dependency tree
299
npm error
300
npm error While resolving: nextjs-typescript-tailwind-capacitor-starter@0.1.0
301
npm error Found: @capacitor/core@7.0.1
302
npm error node_modules/@capacitor/core
303
npm error @capacitor/core@"^7.0.0" from the root project
304
npm error
305
npm error Could not resolve dependency:
306
npm error peer @capacitor/core@"^6.0.0" from @capacitor/browser@6.0.5
307
npm error node_modules/@capacitor/browser
308
npm error @capacitor/browser@"^6.0.4" from the root project
309
npm error
310
npm error Fix the upstream dependency conflict, or retry
311
npm error this command with --force or --legacy-peer-deps
312
npm error to accept an incorrect (and potentially broken) dependency resolution.
313
npm error
314
npm error
315
npm error For a full report see:
316
npm error /home/runner/.npm/_logs/2025-02-12T15_30_49_016Z-eresolve-report.txt
317
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-02-12T15_30_49_016Z-debug-0.logmaybe we need to structure the website project in a different way?
Brian12 months ago
Not sure where to post this GH issue, but I want to bring to your attention that
https://github.com/cloudposse/terraform-provider-awsutils/issues/82
0.20.0 release (released less than hour ago) of cloudposses's awsutils provider is crashing.https://github.com/cloudposse/terraform-provider-awsutils/issues/82