Chris Lopes

This is how I tried put this to work: ``` #/home/chrisandrew/workspace/gomes-hotsite/lib/tasks/vanity_db_fix.rake desc "Migrate the database through scripts in db/migrate." namespace :db do APP_PATH = File.expand_path('../../../', __FILE__) db_conf = YAML::load(File.open(File.join(APP_PATH,'config','vanity.yml'))) DB_VANITY...

@phillbaker I've just checked Vanity 2.2.1 and the behaviour is the same: db:migrate and bd:create still take effect on database defined in database.yml and `FATAL: database "hotsite_vanity_dev" does not exist`...

@phillbaker Forget it! Sorry! I've realized that I needed to re-generate vanity migrations in order to it to work. Considerations: db:migration runs fine, but vanity DB must be created (or...

When I created #6731, I should have stated that while I think this issue may solve my workflow, it seems like a big undertaking and doesn't seem to be a...

Another reason to use Redis streams over pub/sub is that the latter doesn't scale well (I don't have the links right now, but pub/sub performance degrades when more Redis nodes...

Until the new property is added to the queue construct, this can still be worked around within CDK using an escape hatch: ```javascript const cfnQueue = queue.node.defaultChild as CfnResource; cfnQueue.addOverride('Properties.SqsManagedSseEnabled',...

The logger could just support a special "off" LOG_LEVEL and is up to the user to set it accordingly when needed.

Looking forward to this one. My use case: ```JSON "exports": { "./*": [ "./src/*/index.ts", "./src/*.ts" ] }, ``` This way both cases below will work: ```Javascript import { aModuleIndex }...

Also, if this is being considered, the package.json imports have the same issue. It would be great to have alternatives working for both of them.