You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This becomes easier to manage when it;s a cross region deployment.
In my case, pipeline is running in Sydney, but the deployment is in the Melbourne region.
Expected behaviour
Tell us what should happen
artifact_bucket_name - should be optional.
Subject of the issue
Describe your issue here.
Your environment
version of sceptre (sceptre --version)
Sceptre, version 4.5.2
version of python (python --version)
Python 3.11.8
which OS/distro
MacOS
CodeBuild - aws/codebuild/amazonlinux2-x86_64-standard:5.0
Steps to reproduce
Tell us how to reproduce this issue. Please provide sceptre project files if possible,
you can use https://plnkr.co/edit/ANFHm61Ilt4mQVgF as a base.
SAM Package (https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-cli-command-reference-sam-package.html) now has an option to resolve-s3. This automatically creates a bucket in the region specified in the same package command.
This becomes easier to manage when it;s a cross region deployment.
In my case, pipeline is running in Sydney, but the deployment is in the Melbourne region.
Expected behaviour
Tell us what should happen
artifact_bucket_name - should be optional.
Actual behaviour
Tell us what happens instead
"'artifact_bucket_name' is a required property\n\nFailed validating 'required' in schema:\n {'properties': {'artifact_bucket_name': {'type': 'string'},\n 'artifact_prefix': {'type': 'string'},\n 'build_args': {'type': 'object'},\n 'package_args': {'type': 'object'},\n 'path': {'type': 'string'},\n 'skip_jinja_cleanup': {'type': 'boolean'}},\n 'required': ['path', 'artifact_bucket_name'],\n 'type': 'object'}\n\nOn instance:\n {'build_args': {'use-container': True},\n 'package_args': {'region': 'ap-southeast-4', 'resolve-s3': True},\n 'path': 'templates/lambda.yaml.j2'}"
The text was updated successfully, but these errors were encountered: