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.

Sign up for GitHub

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

Jump to bottom

Parameters: [ScalingMinSize, ScalingMaxSize] do not exist in the template #401

Closed
nicholasgriffintn opened this issue Nov 20, 2018 · 3 comments
Closed

Parameters: [ScalingMinSize, ScalingMaxSize] do not exist in the template #401

nicholasgriffintn opened this issue Nov 20, 2018 · 3 comments
Assignees
@mneil
Labels
bug

Comments

@nicholasgriffintn
Copy link

nicholasgriffintn commented Nov 20, 2018 •
edited

hey,

whenever I configure an aurora serverless with a min or max size i get this error:

Parameters: [ScalingMinSize, ScalingMaxSize] do not exist in the template

how do I configure the min . or max size for aurora if not that? because the default 256 is still coming through, which i definitely don't want.

here's the config:

  database:
      name: wordpress
      engine: aurora
      instanceClass: db.t2.small
      iamAuthentication: false
      masterUsername: admin
      engineMode: serverless
      allocatedStorage: 10

      environmentConfig:                        
        acceptance:
          engineMode: serverless
          minSize: 2
          maxSize: 2
        production:
          engineMode: serverless
          minSize: 2
          maxSize: 8
@mneil mneil added the bug label Nov 20, 2018
@mneil mneil self-assigned this Nov 20, 2018
mneil added a commit that referenced this issue Nov 20, 2018
@mneil
Issue #401 - Mismatch ScalingMaxCapacity and ScalingMaxSize
c41712e 
The database template expected Capacity while the database_upserter
set Size as the parameter.
@mneil
Copy link
Contributor

mneil commented Nov 20, 2018

Looks like there's an issue with the expected parameter name in the code. I've opened a PR to get it fixed. It'll should be available next release.

cplee added a commit that referenced this issue Nov 21, 2018
@cplee
Merge pull request #402 from stelligent/issue-401
7a78d59 
Issue #401 - Mismatch ScalingMaxCapacity and ScalingMaxSize
@cplee
Copy link
Contributor

cplee commented Nov 21, 2018

fixed in #402

@cplee cplee closed this as completed Nov 21, 2018
@nicholasgriffintn
Copy link
Author

Thanks for the quick fix will update to that later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mneil mneil

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mneil @cplee @nicholasgriffintn