Implement default replace workflow

[beam-sysuser]

Update: I think this should be part of a larger effort to implement a default replace workflow combined with the ability to detect when an update and replace affect the same resource and only do the replace.

STR:

• Create a security group with tags.
• Update both the security group name (requires a replace) and the tags (can be updated in-place)
• gyro up

⇅ Replace aws::security-group backend/backend (sg-02762bd7db5859b3d) (because of description, name, skipping without a workflow)
· description:  'Limit backend traffic to OpenVPN/SSH' → 'beam-sandbox-production-backend-us-east-1-v1'
· name:  'beam-sandbox backend serial-1' → 'beam-sandbox-production-backend-us-east-1-v1'
· tags:  +{ Name: 'beam-sandbox production backend v1', beam.project: 'beam-sandbox', beam.serial: '1' }

.
.
.

⇅ Replacing aws::security-group backend/backend (sg-02762bd7db5859b3d)

· description:  'Limit backend traffic to OpenVPN/SSH' → 'beam-sandbox-production-backend-us-east-1-v1'

· name:  'beam-sandbox backend serial-1' → 'beam-sandbox-production-backend-us-east-1-v1'

· tags:  +{ Name: 'beam-sandbox production backend v1', beam.project: 'beam-sandbox', beam.serial: '1' }

SKIPPED

[beam-sysuser]

#136

The current idea is to do as much as gyro can. Replace or update based on whether the resource is replaceable, if the resource is not replaceable, update the updatable fields instead.

by PSDHao

[beam-sysuser]

Merged the wrong PR. This doesn't work anyway. Breaks our autoscaling workflow.

by beetlebugorg

[beam-sysuser]

New branches:
https://github.com/perfectsense/gyro/tree/feature/replace-update
https://github.com/perfectsense/gyro-aws-provider/tree/feature/replace-update

After talking with Hyoo, the current idea is to create two changes (replace and update) when appropriate. The idea is subject to changes.

by PSDHao

[beam-sysuser]

#142
After discussion, changed back to having a single change where having update logic within replace.

by PSDHao