v6.0.0-rc1

Full Changelog: v5.0.0...v6.0.0-rc1

v5.0.0

What's Changed

• upgrade to aws provider v5 by @sblack4 in #16

Full Changelog: v4.6.0...v5.0.0

v2.0.4

Full Changelog: v2.0.3...v2.0.4

v4.6.0

What's Changed

• ignore the password too by @sblack4 in #15

If you're using our bitbucket module

terraform state mv \
'module.bitbucket.module.bitbucketdb.aws_db_instance.this_ignore_engine_version[0]' \
'module.bitbucket.module.bitbucketdb.aws_db_instance.this_ignore[0]'

or just this one

terraform state mv \
'module.bitbucketdb.aws_db_instance.this_ignore_engine_version[0]' \
'module.bitbucketdb.aws_db_instance.this_ignore[0]'

Full Changelog: v4.5.0...v4.6.0

v4.5.0

What's Changed

• Update params variable to allow more attributes by @sblack4 in #14

Full Changelog: v4.4.0...v4.5.0

v4.4.0

What's Changed

• Ignore version changes to engine, also update CI by @sblack4 in #13

If you're upgrading from the last version and want to start ignoring the engine version changes without destroying your database here's a command

terraform state mv 'module.bitbucketdb.aws_db_instance.this' 'module.bitbucketdb.aws_db_instance.this_ignore_engine_version[0]'

You may need to adjust the module name

Full Changelog: v4.3.0...v4.4.0

v2.0.3

Full Changelog: v2.0.2...v2.0.3

Ignore changes to engine version

v4.3.0: Merge pull request #12 from desavera/master

• Merge pull request #8 from rhythmictech/implicit-enhanced-monitoring-role

  add support for auto-creation of monitoring role

Change how database name is handled

Also introduces support for automatically creating enhanced monitoring role.

v4.1.0-rc3

fix parameter group family